| 1 |
On Tue, 2001-09-25 at 21:17, Dan Armak wrote: |
| 2 |
> Hi all, |
| 3 |
> |
| 4 |
> The current gentoo-ebuild/incoming was devised when there were 2-3 ebuilds |
| 5 |
> submitted in a week on average, which needed to be organized in a convinient |
| 6 |
> location. Now there are often 2-3 ebuilds per day, so we need to reorganize. |
| 7 |
> In particular, developers should handle things at the gentoo-ebuild level, |
| 8 |
> not the incoming level. |
| 9 |
> |
| 10 |
> I propose any combination of the following. Tell me what you think and |
| 11 |
> propose any other ideas. |
| 12 |
> |
| 13 |
> 0. drobbins, reminder: add the gentoo-ebuild submission rules to the list |
| 14 |
> page! (Although the rules will need to be changed based on what we decide |
| 15 |
> here). |
| 16 |
> |
| 17 |
> 1. Developers with particular interest in an ebuild, such as an ebuild that |
| 18 |
> is the result of a previous discussion with the author, should take it |
| 19 |
> themselves from gentoo-ebuild and edit/commit it to portage. In fact, if |
| 20 |
> there is are established communications between the developer and the author, |
| 21 |
> they needn't go through gentoo-ebuild at all. |
| 22 |
> |
| 23 |
> 2. Authors who want to update their ebuild often (like the mozilla case which |
| 24 |
> had at least 5 versions ubmitted on gentoo-ebuild) might get cvs access to |
| 25 |
> /usr/portage/incoming/username and do what they want in there, then get a |
| 26 |
> developer to move it to portage proper. |
| 27 |
> |
| 28 |
> 3. All developers should scan gentoo-ebuild once in a while, and pick up any |
| 29 |
> ebuilds they are interested in. On the same criteria as they would if the |
| 30 |
> ebuilds were in incoming. |
| 31 |
> |
| 32 |
> 4. If they see an intersting ebuild which however isn't good enough for |
| 33 |
> inclusion in gentoo, i.e. author didn't follow ebuild writing rules, they |
| 34 |
> should reply and instruct the author on making the correct changes. |
| 35 |
> |
| 36 |
> 5. As above, they should answer generic ebuild-writing questions on |
| 37 |
> gentoo-ebuild. |
| 38 |
> |
| 39 |
> 6. An ebuild that isn't picked up by anyone for say a 2-day limit can be |
| 40 |
> placed in incoming as now done. |
| 41 |
> |
| 42 |
> |
| 43 |
|
| 44 |
Sounds fair, since you are not the only developer that feels that |
| 45 |
incoming is getting to clutterd it seems. |
| 46 |
|
| 47 |
Greetings, |
| 48 |
MS |
Archives