From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] SRC_URI behaviour
Date: Sat, 15 Jun 2013 16:16:59 -0400 [thread overview]
Message-ID: <51BCCBBB.5010902@gentoo.org> (raw)
In-Reply-To: <51BC8B9B.9020301@gentoo.org>
On 06/15/2013 11:43 AM, Luca Barbato 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.
>
> lu
>
There was a period where Zorry and I were working on the hardened
toolchain off the hardened-dev overlay. Migrating it back to the tree
was a pita. Unless the stuff in the overlay is orthogonal to the main
tree, you will effectively be creating forks which are not easily
merged. Repositories in other distros (eg debian) normally just add new
.debs. They don't override deeper structures such as toolchains and
core utilities. We can overrride *anything* in the portage tree like
eclasses making overlays a more serious matter.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
next prev parent reply other threads:[~2013-06-15 20:16 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
2013-06-15 16:37 ` Ciaran McCreesh
2013-06-16 7:52 ` Arfrever Frehtes Taifersar Arahesis
2013-06-15 20:16 ` Anthony G. Basile [this message]
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=51BCCBBB.5010902@gentoo.org \
--to=blueness@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