-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Marcus D. Hanwell wrote: | I was considering the possibility of using a repo specific keyword in ebuilds | such as ~sci so that any herd testers and/or users can add that to their | ACCEPT_KEYWORDS in /etc/make.conf (as well as maintaining normal keyword | practices). The intention is to add stuff to the repo for testing before it | is ready to go into portage. Some stuff that we just can't maintain for | whatever reason could possibly end up in their more permanently too.
I don't really see the point of ~sci, since the rest of the ebuild will probably need to get diffed against the regular tree anyway if there are any changes. How do you plan to keep this in sync with changes in the regular tree? How is our own solution superior to getting together with gentopia or something similar that already exists? | It provides a great way to train herd testers in a safer (than the main | portage tree) repository and develop ebuilds more interactively. Once stuff | is moved into the portage tree it should of course be deleted from the | repository. OK, so this overlay is only for new packages, and not for changes to existing ones? Thanks, Donnie -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDnKfnXVaO67S1rtsRAvpaAKClKSabM7+ImQOJ7onA2fifAdUiIACfSx3h W1DCMkAWInmrJgmUuPKfotM= =6QrV -----END PGP SIGNATURE----- -- [email protected] mailing list
