| 1 |
On Fri, Jul 26, 2002 at 01:03:27PM -0500, Jean-Michel Smith wrote: |
| 2 |
> It is a tough call where to draw the line of responsiblity. Do you make |
| 3 |
> ebuild maintainers do the work in their ebuild, in which case only those |
| 4 |
> whose maintainers have any interest in such a feature will use the feature, |
| 5 |
> and the rest will be left out anyway, or do you have an ebuild that maintains |
| 6 |
> such files for all the rest of the ebuilds, that a person who is interested |
| 7 |
> in the feature can maintain across a bunch of packages (e.g. |
| 8 |
> update-menu-configs)? |
| 9 |
> |
| 10 |
> I think the best solution is one that allows ebuild maintainers to add the |
| 11 |
> information for their ebuild if they wish, but also allows other interested |
| 12 |
> parties to add information for ebuilds whose maintainers do not have the time |
| 13 |
> or interest to maintain that sort of information themselves. |
| 14 |
> |
| 15 |
> Soemthing like: |
| 16 |
> |
| 17 |
> #1 an optional ebuild that installs the auto-menu system |
| 18 |
> #2 an ebuild containing menu information/config info for a plethora of ebuilds |
| 19 |
> out there. |
| 20 |
> #3 a documented means by which individual ebuilds can overlay/override the |
| 21 |
> config file in #2 above, or an easy way for ebuild maintainers to submit |
| 22 |
> changes/updates to #2 above. |
| 23 |
|
| 24 |
I believe that Mandrake uses the #2 method, but I can not say that I |
| 25 |
really like it. My main problem with it is that whoever is in charge of |
| 26 |
that one giant package of menufiles is responsible for understanding |
| 27 |
every single package in the portage system. If you know what is in a |
| 28 |
package then writing a menufile would only take 30 seconds or so, but it |
| 29 |
is not so easy when you have to find out what is in a package and what |
| 30 |
it does before you can write it. |
| 31 |
Keeping the menufiles with the packages they belong to is the more |
| 32 |
appropriate thing to do in my oppinion, and we shouldn't let lazy |
| 33 |
maintainers change that. If a maintainer does not add a menufile for |
| 34 |
their package, then you should submit a bug about it. That way the menu |
| 35 |
entry at least gets looked at by the maintainer, in case they disagree |
| 36 |
with part of it, or so they kow about it in case they want to chage |
| 37 |
something about it in the future. |
| 38 |
If after a while we see that it really isn't working out, then we can |
| 39 |
always do a big menufile package at that time. |
Archives