| 1 |
On Sat, Jun 15, 2013 at 11:43 AM, Luca Barbato <lu_zero@g.o> wrote: |
| 2 |
> On 06/15/2013 05:33 PM, Rich Freeman wrote: |
| 3 |
>> On Sat, Jun 15, 2013 at 11:24 AM, Brian Dolbec <dolsen@g.o> wrote: |
| 4 |
>>> The other thing is that would put a mandatory system requirement on |
| 5 |
>>> layman which many of the devs would be opposed to. But, there is an open |
| 6 |
>>> bug calling for it to be merged with portage... |
| 7 |
>> |
| 8 |
>> Honestly, native support for overlays is something paludis gets right |
| 9 |
>> - the main tree is just another tree and you prioritize them. |
| 10 |
> |
| 11 |
> Not sure it is a great idea in practice. |
| 12 |
|
| 13 |
This is how virtually all other distros operate - they ship with a |
| 14 |
list of repositories and the user controls which ones are in use. All |
| 15 |
such a change would do is make it easier to manage overlays - you'd |
| 16 |
certainly not be required to use them. Plus, right now with Gentoo |
| 17 |
there is no way to set an overlay as being LOWER priority than the |
| 18 |
main tree - so that you can grab packages not supported in main from |
| 19 |
an overlay but still use the main packages when available. That is, |
| 20 |
unless you set up the overlay as your main tree and set up portage as |
| 21 |
an overlay. |
| 22 |
|
| 23 |
The approach paludis uses just seems simpler all-around, minus the |
| 24 |
fact that it doesn't provide defaults for internals that need not be |
| 25 |
exposed (vdb and such - which admittedly aren't needed by exherbo). |
| 26 |
|
| 27 |
Rich |
Archives