From: Jon Portnoy <avenj@gentoo.org>
To: Cedric Veilleux <cedric@neopeak.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Binary release of gentoo
Date: Thu, 10 Apr 2003 04:29:11 -0400 [thread overview]
Message-ID: <20030410082911.GA23008@cerberus.oppresses.us> (raw)
In-Reply-To: <200304100429.01001.cedric@neopeak.com>
On Thu, Apr 10, 2003 at 04:29:00AM -0400, Cedric Veilleux wrote:
> > > I thought it was called Debian? ;o)
> > >
> > > Or perhaps, "I'd eat meat, if only it were vegetarian"
> > >
> > > Seriously though, I don't see the point, unless you want to sell more
> > > T-Shirts, there are a plethora of good binary distributions of linux out
> > > there already and all the downsides you list are what, imo, define
> > > Gentoo.
> > >
> > > I'd prefer to see gentoo improved as a source-based distribution
> >
> > Ditto. There is no point to a binary version of Gentoo. If you want that
> > then as Michael said just use Debian.
>
>
> I don't agree. Gentoo already supports binary packages anyways (emerge -b /
> emerge -k). We're only talking about improving it AFAIK.. What's wrong with
> improving some features of portage if it's possible and if it won't hurt
> anyone?
>
It's not a question of improving it so much as the distribution
resources required.
I'm not sure you understand the full extent of the problems with
distributing binary packaging. The short story is:
Besides loss of flexibility, it's a QA nightmare. It also requires a
massive infrastructure behind it in terms of putting binary packages
online for people to download. We don't have space on our mirrors, we're
not very likely to host something like that - the resources just aren't
there, frankly, and it doesn't seem very productive for us to dedicate
those resources to binary distribution when we're a source-based
distribution...
If someone wanted to do something like this independently, I think that
would be an excellent resource to a lot of people. However, you need to
consider the full implications - it's not as simple as it seems on the
surface...
--
Jon Portnoy
avenj/irc.freenode.net
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-10 8:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-10 0:13 [gentoo-dev] Binary release of gentoo Noah Justin Norris
2003-04-10 6:28 ` leahcim
2003-04-10 7:03 ` Robert Cole
2003-04-10 8:29 ` Cedric Veilleux
2003-04-10 8:29 ` Jon Portnoy [this message]
2003-04-10 8:55 ` leahcim
2003-04-10 9:07 ` Henti Smith
2003-04-10 9:41 ` Spider
2003-04-10 9:49 ` Henti Smith
2003-04-10 16:30 ` [gentoo-dev] " Peter Simons
2003-04-11 8:14 ` [gentoo-dev] " Miles Egan
2003-04-11 2:01 ` DJ Cozatt
2003-04-11 14:43 ` Dan Armak
2003-04-11 16:11 ` Jon Kent
2003-04-10 10:54 ` Noah Justin Norris
2003-04-10 7:27 ` Spider
2003-04-10 8:13 ` Cedric Veilleux
2003-04-10 8:45 ` Spider
2003-04-11 8:16 ` Miles Egan
2003-04-10 15:52 ` Robin H.Johnson
2003-04-10 18:57 ` Jon Portnoy
2003-04-11 0:51 ` Spider
2003-04-10 8:08 ` Dylan Carlson
2003-04-10 18:50 ` Matt Thrailkill
2003-04-10 19:34 ` Dan Armak
2003-04-10 21:54 ` Mark Farver
2003-04-10 22:17 ` Dan Armak
2003-04-10 23:01 ` Matt Thrailkill
2003-04-11 1:55 ` Terje Kvernes
2003-04-11 14:42 ` Dan Armak
2003-04-11 10:17 ` Noah Justin Norris
2003-04-11 5:48 ` C. Brewer
2003-04-11 4:20 ` John White
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=20030410082911.GA23008@cerberus.oppresses.us \
--to=avenj@gentoo.org \
--cc=cedric@neopeak.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