| 1 |
Howdy, |
| 2 |
|
| 3 |
While attempting to try the latest version of ruby-gnome2 (0.19.1), I |
| 4 |
copied the 0.19.0 ebuilds to my local overlay then renamed them to the |
| 5 |
new version. I then downloaded the ruby-gnome2-all-0.19.1.tar.gz, |
| 6 |
placed it in /usr/portage/distfiles, then used "ebuild ruby-... |
| 7 |
digest" for each of the packages to create the Manifest file. |
| 8 |
|
| 9 |
When I attempt to emerge the updated packages, the first package, ruby- |
| 10 |
glib2-0.19.1, errors with a detected file collision on /usr/lib/ |
| 11 |
pkgconfig. This is a directory and thus emerge finds every package |
| 12 |
that has installed a file in it. |
| 13 |
|
| 14 |
Now my guess is that some code that attempts to check for conflicts |
| 15 |
within the /usr/lib/pkgconfig directory is being given an blank |
| 16 |
package name, thus is checking the directory. My problem is I don't |
| 17 |
see where the conflict code is even called. Anyone have any hints or |
| 18 |
know where the documentation is? |
| 19 |
|
| 20 |
TIA, |
| 21 |
Roy |
Archives