From: Dylan Carlson <absinthe@gentoo.org>
To: Noah Justin Norris <gentoo@mchsi.com>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Binary release of gentoo
Date: Thu, 10 Apr 2003 04:08:15 -0400 [thread overview]
Message-ID: <200304100408.15866.absinthe@gentoo.org> (raw)
In-Reply-To: <200304100013.30307.gentoo@mchsi.com>
On Wednesday 09 April 2003 08:13 pm, Noah Justin Norris wrote:
> Is there any interest to start a binary release of gentoo with
> precompiled binaries. Im talking the entire source tree i know many
> people that would switch to gentoo if they would not have to compile
> every thing from source . not everyone has the fastest computer out
> there.
A "binary release of Gentoo" is out of scope for what Gentoo is trying to
provide. We are primarily a source-based distribution, and that's where
our priorities are set. Compiling the OS from scratch is not for
everyone, which we recognize and that's fine ...
There are some packages which make sense to have prebuilt binary options,
namely Java classes... and large packages which strip CFLAGS at compile
time, or ones that otherwise don't have any advantage of being compiled
from source. We would be very selective of the packages which actually
use this feature, as we are about -bin packages currently.
The topic of source-or-binary ebuilds (user selectable) is actively being
debated in -core. Several options are being discussed as to what angle
we might pursue. The aim is an appropriate solution to allow for _some_
situations where binaries can be installed without cluttering the portage
tree with -bin directories. Currently on the table for review is adding
a prebuilt USE flag. Some are for it, some are against it. I'm sure
you'll hear about it when/if anything gets decided.
[...]
My general stance is that if someone wants a full binary OS release, they
should pursue something like Debian, Slackware, et al. That's their core
competency... ours is building from source. There's no right or wrong
either way, it just depends on what you're after.
Cheers,
Dylan Carlson
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x708E165F
Key fingerprint = 3AEA DE38 FE42 15A6 C0E2 730E 3D04 BCC1 708E 165F
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-04-10 8:08 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
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 [this message]
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=200304100408.15866.absinthe@gentoo.org \
--to=absinthe@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo@mchsi.com \
/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