1 |
Henti Smith [bain@×××××××.za] wrote: |
2 |
> here follows the proposal: |
3 |
> |
4 |
[snip] |
5 |
> this proposal sounds good from the developers side .. but shows very little |
6 |
> leeway for user contributed interaction which from reading many mails and |
7 |
> discussions seems to be the real problem. The users contribute and it takes a |
8 |
> long time for a responce. this system will make ebuild responcibility inside |
9 |
> the development group easer to assign .. but if as was proposed, a package |
10 |
> needs a dedicated developer .. and one does not rise to take it .. it gets |
11 |
> dropped .. |
12 |
> |
13 |
|
14 |
Hrm. I'm not sure how you're planning to handle dropping packages, but |
15 |
perhaps they could be flagged in some way, either server side or in the |
16 |
ebuild itself, and a tool could be provided within the portage tools |
17 |
group to do a check and see if any of the packages currently in use on |
18 |
a machine are scheduled to be dropped? Preferably something we could |
19 |
run in a cron job...i.e. not a graphical client. |
20 |
|
21 |
-- |
22 |
gentoo-dev@g.o mailing list |