| 1 |
On Mon, 2003-09-08 at 04:08, Jan Krueger wrote: |
| 2 |
|
| 3 |
> > > Again examples from the actual tree, so you can try yourself: |
| 4 |
> > > 1. emerge ezmlm and emerge ezmlm-idx |
| 5 |
> > > providing slightly different funtionality they will overwrite each other |
| 6 |
> > > (instead of blocking each other) |
| 7 |
> > |
| 8 |
> > Bug. Is it filed? |
| 9 |
> Bug in portage! portage is the one that allows such integrity mess. |
| 10 |
> |
| 11 |
|
| 12 |
Whoever just forgot to add a 'DEPEND="!ezmlm-idx"' to ezmlm, and |
| 13 |
reverse for ezmlm-idx ? I do not see how portage will cause that |
| 14 |
individual(s) to forget about that ? |
| 15 |
|
| 16 |
> > So we don't have enough manpower. |
| 17 |
> Thats true for many open-source project. Some of them just try to get |
| 18 |
> organized more efficiently and succeed in doing so. |
| 19 |
> So, maybe there is a more appropriate organization model for gentoo? |
| 20 |
> |
| 21 |
|
| 22 |
I am also guessing you have not read GWN, and -dev for the last two |
| 23 |
months or so ? |
| 24 |
|
| 25 |
> > > And to me its clear why it is like that (at least on reason): |
| 26 |
> i meant to say: (at least one reason) |
| 27 |
> sorry. |
| 28 |
> |
| 29 |
> > So basically you're saying portage shouldn't install software. |
| 30 |
> I say: |
| 31 |
> portage must respect my system inegrity! |
| 32 |
> |
| 33 |
|
| 34 |
Ok, but the merge code in portage could have a bug bigger than anything |
| 35 |
pkg_{post,pre}inst() could ever cause. Right, so that is why we need |
| 36 |
all the other safety nets - they could be more buggy ? |
| 37 |
|
| 38 |
> > So we should never be able to tweak config files et al in an ebuild? |
| 39 |
> an ebuild may freely modify its own config files. |
| 40 |
> modification of config files not belonging to the ebuild should be done via an |
| 41 |
> already suggested, secure abstraction, lets say a function like: |
| 42 |
> changeconf phph.ini "line to add to phpini" |
| 43 |
> portage could then intercept, respecting the suggested CONFIG_EXCLUDE or other |
| 44 |
> user settings, or, if no user setting is the way, go to apply the change. |
| 45 |
> This way it would be impossible for the ebuild to wipe php.ini. |
| 46 |
> Also the user, via CONFIG_EXCLUDE, may completely switch of editing of php.ini |
| 47 |
> by ebuilds. On the other hand, if the user doesnt care, the ebuild is free to |
| 48 |
> add this line to php.ini. |
| 49 |
> |
| 50 |
|
| 51 |
Some times it is not so easy. |
| 52 |
|
| 53 |
Unfortunately black and white on paper usually is much more seperate |
| 54 |
issues than real live could ever be. |
| 55 |
|
| 56 |
|
| 57 |
-- |
| 58 |
|
| 59 |
Martin Schlemmer |
| 60 |
Gentoo Linux Developer, Desktop/System Team Developer |
| 61 |
Cape Town, South Africa |
Archives