From: Peter Fein <pfein@pobox.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Several portage trees
Date: Fri, 25 Apr 2003 10:10:49 -0500 [thread overview]
Message-ID: <20030425101049.0c6fb930.pfein@pobox.com> (raw)
In-Reply-To: <3EA92BE5.4030003@foser.dyn.warande.net>
On Fri, 25 Apr 2003 14:36:53 +0200
foser <foser@foser.dyn.warande.net> wrote:
> Francisco Gimeno wrote:
> > Hi
> >
> > I was wondering about having several portage trees to allow external
> > distributor having repositories of packages.
> <snip>
> > It could be really useful, if we could use something like it
>
> This has been brought up before and I personally do not really like the
> idea too much, i think it makes the distro less reliable as whole if we
> add options like this. People will start using repositories here and
> there and in the end we will get bugreports on ebuilds we never approved
> or even saw (and some ebuilds can have far reaching effects). No, i
> think 'external distributors' should try and go trough the normal
> channels and get their ebuilds Gentoo approved.
I think a note saying "DON"T DO THIS UNLESS YOU REALLY KNOW WHAT YOU'RE DOING",
as is done elsewhere would suffice. Given the recent volume on ebuild approval,
that's not much of an counter-argument. I agree that inclusion in Gentoo-proper
is a worthy goal - but as a user, not being restricted to blessed packages
should be my choice (and of course, no one's under any obligation to support any
of this to begin with, but it's worth discussing). Maybe I'm less scared of
stability issues running Gentoo on a home box that could erupt into flames
without causing me much distress, but this should be a matter of choice, rather
than a policy enforced by software. Such a scheme may actually speed up package
acceptance, as it provides a wider test base prior to inclusion.
> >
> > I think it solves a lot of complains about flexibility and edging of Gentoo.
> >
>
> What complaints ? Is it so hard to download an ebuild in put it in your
> local overlay ? The extra step required does make sure you are aware
> that you are using non-approved ebuilds.
I'd be aware I'd be using non-approved ebuilds if I set those vars in the first
place & portage warned/notified me which repository it was installing from.
This architecture rocks - restricting it to approved packages only deprives
folks of a really great tool (wow, I'm sounding awfully "software wants to be
free" today...).
--Pete
--
Peter Fein
pfein@pobox.com
773-575-0694
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-25 15:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 10:52 [gentoo-dev] Several portage trees Francisco Gimeno
2003-04-25 12:36 ` foser
2003-04-25 15:10 ` Peter Fein [this message]
2003-04-25 16:32 ` foser
2003-04-25 18:23 ` Todd Berman
2003-04-25 19:09 ` Peter Fein
2003-04-25 19:02 ` George Shapovalov
2003-04-25 19:45 ` Peter Fein
2003-04-26 7:05 ` Joseph Carter
-- strict thread matches above, loose matches on Subject: below --
2003-04-25 13:04 Francisco Gimeno
2003-04-25 16:34 Joshua Brindle
2003-04-25 19:57 ` kikov
2003-04-25 21:00 ` Robin H.Johnson
2003-04-26 2:08 ` Daniel Armyr
2003-04-25 20:07 Joshua Brindle
2003-04-26 0:30 ` foser
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=20030425101049.0c6fb930.pfein@pobox.com \
--to=pfein@pobox.com \
--cc=gentoo-dev@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