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