1 |
With the new split in Portage where system set packages are not |
2 |
considered in an "emerge -auDNv world" unless something in world |
3 |
RDEPENDs on it brings about a few issues. |
4 |
|
5 |
i.e. Portage implicitly has a run time dependency on app-arch/tar, |
6 |
app-arch/bzip2, app-arch/gzip, app-arch/lzma due to the fact that |
7 |
Portage will use these utilities when "unpack" is called inside of an |
8 |
ebuild. As such these are run time depends of Portage and need to be in |
9 |
RDEPEND (the same would technically be true for pkgcore and paludis, |
10 |
unless they use tar's support for those formats and then its up to tar |
11 |
to depend properly). |
12 |
|
13 |
This brings out the fun of circular depends. I don't really know how to |
14 |
address this but a lot of packages are going to have to be updated to |
15 |
contain proper depends. i.e. C based apps will need |
16 |
RDEPEND="virtual/libc". C++ packages will need a stdc++ depend. |
17 |
|
18 |
If you're running Portage 2.2_rc1 on a system you can see if any |
19 |
packages have begun to slack behind on your system in the system set. |
20 |
|
21 |
emerge -puv @system |
22 |
|
23 |
You might notice packages in here that are used on a daily basis but are |
24 |
now no longer being updated. |
25 |
-- |
26 |
gentoo-dev@l.g.o mailing list |