I ran 'emerge autopano-sift' which first installed the gtk-sharp and glade-sharp packages. The autopano-sift build failed though because pkg-config couldn't find the gtk-sharp.pc or glade-sharp.pc files (in /usr/lib64/pkgconfig). This happened because the first two packages installed the following files: >>> /usr/lib64/pkgconfig/gtk-sharp-2.0.pc >>> /usr/lib64/pkgconfig/glade-sharp-2.0.pc Should the relevant ebuilds also create symlinks to these that don't contain the version numbers? Reproducible: Always Steps to Reproduce: 1. 2. 3.
Please do not assign bugs unless you know where they go, reassigning to dotnet.
Assigning to the right folks finally. Halcy0n: *-sharp-2.3.x came out of package.mask recently. The *-sharp-1.0.x and *-sharp-2.{3,5}.x stuff goes into the 1 and 2 SLOT respectively. A package can compile against one or the other. Since autopano-sift seems to compile against *-sharp-1.0.x, and not the 2.x SLOT stuff, the deps should reflect that. Peter: I can see where the confusion might have come in, but the *-sharp stuff is correct. the *-sharp-1.0 ebuilds install the *-sharp.pc files, and the newer *-sharp-2.x stuff installs the versioned *-sharp-2.0.pc files, since they are different, parallel installable libraries.
Fixed in the tree. Thanks.
