public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] SRC_URI behaviour
Date: Sat, 15 Jun 2013 11:51:03 -0400	[thread overview]
Message-ID: <CAGfcS_=6cstiwCM6hm7DWBCTw52ZLgHsrHJpDZNkPQOBY8DLHA@mail.gmail.com> (raw)
In-Reply-To: <51BC8B9B.9020301@gentoo.org>

On Sat, Jun 15, 2013 at 11:43 AM, Luca Barbato <lu_zero@gentoo.org> wrote:
> On 06/15/2013 05:33 PM, Rich Freeman wrote:
>> On Sat, Jun 15, 2013 at 11:24 AM, Brian Dolbec <dolsen@gentoo.org> wrote:
>>> The other thing is that would put a mandatory system requirement on
>>> layman which many of the devs would be opposed to. But, there is an open
>>> bug calling for it to be merged with portage...
>>
>> Honestly, native support for overlays is something paludis gets right
>> - the main tree is just another tree and you prioritize them.
>
> Not sure it is a great idea in practice.

This is how virtually all other distros operate - they ship with a
list of repositories and the user controls which ones are in use.  All
such a change would do is make it easier to manage overlays - you'd
certainly not be required to use them.  Plus, right now with Gentoo
there is no way to set an overlay as being LOWER priority than the
main tree - so that you can grab packages not supported in main from
an overlay but still use the main packages when available.  That is,
unless you set up the overlay as your main tree and set up portage as
an overlay.

The approach paludis uses just seems simpler all-around, minus the
fact that it doesn't provide defaults for internals that need not be
exposed (vdb and such - which admittedly aren't needed by exherbo).

Rich


  reply	other threads:[~2013-06-15 15:51 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15  8:56 [gentoo-dev] [RFC] SRC_URI behaviour Vadim A. Misbakh-Soloviov
2013-06-15 11:50 ` Diego Elio Pettenò
2013-06-15 12:12   ` Rich Freeman
2013-06-15 12:14     ` Diego Elio Pettenò
2013-06-15 13:06       ` Rich Freeman
2013-06-15 13:15         ` Diego Elio Pettenò
2013-06-15 13:26           ` Andreas K. Huettel
2013-06-15 21:15       ` Michael Weber
2013-06-15 21:17         ` Diego Elio Pettenò
2013-06-15 21:19           ` Diego Elio Pettenò
2013-06-15 21:21           ` Michael Weber
2013-06-15 21:24             ` Markos Chandras
2013-06-15 21:40               ` Michael Weber
2013-06-15 21:25             ` Diego Elio Pettenò
2013-06-15 22:38         ` Rick "Zero_Chaos" Farina
2013-06-15 13:34     ` Ulrich Mueller
2013-06-15 13:37       ` Diego Elio Pettenò
2013-06-15 13:47         ` Ulrich Mueller
2013-06-15 13:57           ` [gentoo-dev] " Michael Palimaka
2013-06-15 13:59           ` [gentoo-dev] " Diego Elio Pettenò
2013-06-15 12:34   ` Vadim A. Misbakh-Soloviov
2013-06-15 13:50     ` Luca Barbato
2013-06-15 12:48   ` Alexander V Vershilov
2013-06-15 12:58     ` Diego Elio Pettenò
2013-06-15 14:22   ` Pacho Ramos
2013-06-15 13:05 ` Michał Górny
2013-06-15 13:11   ` Vadim A. Misbakh-Soloviov
2013-06-15 13:16     ` Diego Elio Pettenò
2013-06-15 15:24   ` Brian Dolbec
2013-06-15 15:33     ` Rich Freeman
2013-06-15 15:43       ` Luca Barbato
2013-06-15 15:51         ` Rich Freeman [this message]
2013-06-15 16:37           ` Ciaran McCreesh
2013-06-16  7:52           ` Arfrever Frehtes Taifersar Arahesis
2013-06-15 20:16         ` Anthony G. Basile
2013-06-16  0:24   ` Zac Medico
2013-06-16 11:46     ` Luca Barbato
2013-06-16 12:12     ` Georg Rudoy
2013-06-16 12:18     ` Vadim A. Misbakh-Soloviov
2013-06-16 13:41     ` [gentoo-dev] " Michael Palimaka
2013-06-16 14:39     ` [gentoo-dev] " Rick "Zero_Chaos" Farina
2013-06-15 15:12 ` Rick "Zero_Chaos" Farina
2013-06-15 21:31   ` Michael Weber
2013-06-15 16:35 ` Ciaran McCreesh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGfcS_=6cstiwCM6hm7DWBCTw52ZLgHsrHJpDZNkPQOBY8DLHA@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox