public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Miles Egan <miles@caddr.com>
To: robert.cole@support4linux.com
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Binary release of gentoo
Date: Fri, 11 Apr 2003 01:14:01 -0700	[thread overview]
Message-ID: <3E967949.8030208@caddr.com> (raw)
In-Reply-To: <200304100003.57256.robert.cole@support4linux.com>

Robert Cole wrote:
> On Wednesday 09 April 2003 11:28 pm, leahcim@ntlworld.com wrote:
> 
>>On Thu, Apr 10, 2003 at 12:13:30AM +0000, 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.
>>
>>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.

Actually I think a binary version would be pretty cool.  I use Gentoo 
mainly because it tracks new versions of packages so much better than 
debian.  In fact, I think I switched from debian out of frustration 
waiting for debian to package kde 3.1.  Compiling from source is cool 
too but it's not what keeps me on Gentoo.

miles


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-04-10 15:15 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     ` Miles Egan [this message]
2003-04-11  2:01       ` [gentoo-dev] " 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=3E967949.8030208@caddr.com \
    --to=miles@caddr.com \
    --cc=gentoo-dev@gentoo.org \
    --cc=robert.cole@support4linux.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