| 1 |
Dan Armak <danarmak@g.o> writes: |
| 2 |
|
| 3 |
> Good idea. Dan, go ahead and create and add a /usr/portage/incoming |
| 4 |
> >directory to CVS and check all new ebuilds in there. Then, post a |
| 5 |
> >wiki item for each new ebuild (or batch of related ebuilds) and |
| 6 |
> >assign the wiki item to the appropriate team, priority "low". Thanks |
| 7 |
> >for doing this. |
| 8 |
> > |
| 9 |
> OK. Should I classify the ebuilds as well and have e.g. |
| 10 |
> /usr/portage/incoming/app-text? |
| 11 |
|
| 12 |
Isn't it better if the team (which should have the best idea of where |
| 13 |
it should go) put them in the right directory? That will also make it |
| 14 |
easier on the one that puts them in incoming. |
| 15 |
|
| 16 |
Regards, |
| 17 |
Mikael Hallendal |
| 18 |
|
| 19 |
-- |
| 20 |
Mikael Hallendal micke@×××××××××××.se |
| 21 |
CodeFactory AB http://www.codefactory.se/ |
| 22 |
Office: +46 (0)8 587 583 05 Cell: +46 (0)709 718 918 |
Archives