Re: [gentoo-dev] GLEP 19, reloaded (again)

[Jeremy Maitin-Shepard <jbms@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]

Spider <spider@gentoo.org> writes:

> [snip]

> We had to scrap both Gentoo -and- Debian stable trees. Why?  Because
> both update the -main- repository when releasing security fixes/
> bugfixes. Neither have a stable tree thats archived once and never
> changes.

> If you have to actively change a tree (modifications directly into the
> "frozen" tree) which is the case in many environmens, you get stuck with
> this problem. if upstream ever changes their tree, work is lost. You can
> separate local trees and so on, however, once again work is lost when
> internal revisions have superceeded the ones in the tree. (fex, local
> changes to sshd to patch ther initscripts and default config files
> before rollout, which ups the revision of openssh a few times, and then
> there is a backported securityfix?  It won't get merged. )

If you want a tree that doesn't change, you can simply not update it
(from the Gentoo mirrors).  This is particularly easy if you are running
your own internal rsync mirror, since then you don't even have to worry
about not having a convenient mechanism for distributing the portage
tree to the users.  This requires no work from Gentoo -- what does
require significant work, and what some users want, is a tree that is
only updated with bug fixes.


-- 
Jeremy Maitin-Shepard

[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]