Grive needs libgrive.so.0 ?

[tforsman]

As you might know already, im packaging grive for Foresight. But it looks like grive wants libgrive.so.0. And wonder where that might come from?
If grive creates it, the code makes grive depend on it. And that's not good.

warning: EnforceSonameBuildRequirements: The following dependencies are not resolved within the package or in the system database: ['soname: ELF64/libgrive.so.0(SysV x86_64)']
warning: EnforceSonameBuildRequirements: The package may not function if installed, and Conary may require the --no-deps option to install the package.

There is a way to overwrite this, but still it's somehow wrong.

[match065]

yes. libgrive should be built along with grive and grive depends on it. I guess it should be because the cmake rules doesn't install it.

Massimo, can you take a look?

[nestal]

I tried 0.0.4 and find that libgrive is created at the prefix (which is /usr/local by default). Can it be built successfully in Foresight?

[tforsman]

Some changes in grive demanded some changes in how we build it in Foresight.
Just re-checked everything and now builds normally and working as a charm.

It doesn't ask anymore about libgrive.so*** and it's added as it should.