1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Marcus D. Hanwell wrote: |
5 |
| I was considering the possibility of using a repo specific keyword in |
6 |
ebuilds |
7 |
| such as ~sci so that any herd testers and/or users can add that to their |
8 |
| ACCEPT_KEYWORDS in /etc/make.conf (as well as maintaining normal keyword |
9 |
| practices). The intention is to add stuff to the repo for testing |
10 |
before it |
11 |
| is ready to go into portage. Some stuff that we just can't maintain for |
12 |
| whatever reason could possibly end up in their more permanently too. |
13 |
|
14 |
I don't really see the point of ~sci, since the rest of the ebuild will |
15 |
probably need to get diffed against the regular tree anyway if there are |
16 |
any changes. |
17 |
|
18 |
How do you plan to keep this in sync with changes in the regular tree? |
19 |
How is our own solution superior to getting together with gentopia or |
20 |
something similar that already exists? |
21 |
|
22 |
| It provides a great way to train herd testers in a safer (than the main |
23 |
| portage tree) repository and develop ebuilds more interactively. Once |
24 |
stuff |
25 |
| is moved into the portage tree it should of course be deleted from the |
26 |
| repository. |
27 |
|
28 |
OK, so this overlay is only for new packages, and not for changes to |
29 |
existing ones? |
30 |
|
31 |
Thanks, |
32 |
Donnie |
33 |
-----BEGIN PGP SIGNATURE----- |
34 |
Version: GnuPG v1.4.2 (GNU/Linux) |
35 |
|
36 |
iD8DBQFDnKfnXVaO67S1rtsRAvpaAKClKSabM7+ImQOJ7onA2fifAdUiIACfSx3h |
37 |
W1DCMkAWInmrJgmUuPKfotM= |
38 |
=6QrV |
39 |
-----END PGP SIGNATURE----- |
40 |
-- |
41 |
gentoo-science@g.o mailing list |