-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Zac Medico wrote:
> If we do this then I want to make sure everybody is prepared for the
> consequences. Basically, it restricts implicit RDEPEND to the ebuild level,
> making it independent of whatever RDEPEND may or may not be defined in the
> inherited eclasses. That means that some ebuilds will get implicit RDEPEND
> that they don't get currently. Also, some ebuilds will loose some implicit
> RDEPEND that they current get from eclasses.
I've generated some data to show what the differences in RDEPEND will be after
the
patch has been applied. The data includes a list of affected packages [1], and
two
separate files (tab separated values) for those packages that will have an
implicit
RDEPEND decrease [2] and those that will have an implicit RDEPEND increase [3].
The
format is:
${CATEGORY}/${PF} <tab> RDEPEND before patch <tab> RDEPEND after patch
Fortunately, I don't anticipate that this change will cause significant
disruption.
My plan is to release a sys-apps/portage-2.1.1-r2 revbump masked by
package.mask and
have all of the arch teams keyword it. The ebuild will have an ewarn message in
pkg_postinst() that instructs gentoo-x86 cvs users to clean out their existing
cache
and regenerate it from scratch.
After all of the teams have keyworded portage-2.1.1-r2, I'll unmask it and
apply the
patch on the master rsync mirror. The only extra load on the rsync mirrors
will be
for the cache entries of approximately 2700 packages [1]. The combined total
size of
these cache entries will be approximately 1.5 megabytes. For comparison, cache
entry
updates average approximately 425 per day, but in those cases there is
additional
overhead for changes in ebuilds, eclasses, and auxiliary files. For the ~2700
cache
entries that need to be regenerated after application of the patch, only the
cache
entries alone will incur load on the rsync mirrors. The new version of portage
will
include a patch that will cause it to automatically recognize the changed
RDEPEND
after a sync (unlike earlier versions of portage that relied on mtime alone).
Anyone concerned about the impact of this patch on any packages that they
maintain
should check the list of packages [1] to see if they are affected. Please do
that
and let me know if you anticipate any problems.
Thanks,
Zac
[1]
http://dev.gentoo.org/~zmedico/bug_153591/data/20061104/package_names.txt.bz2
[2]
http://dev.gentoo.org/~zmedico/bug_153591/data/20061104/rdepend_decrease.csv.bz2
[3]
http://dev.gentoo.org/~zmedico/bug_153591/data/20061104/rdepend_increase.csv.bz2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFTV5Z/ejvha5XGaMRApbiAKCWDEU1gjK3NaH0xQmTt7CT8ITHsACgk56y
JdiNGWgX5BpX5cZ+sgxkEfo=
=g2g4
-----END PGP SIGNATURE-----
--
[email protected] mailing list
