public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Spider <spider@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Binary release of gentoo
Date: Thu, 10 Apr 2003 10:45:06 +0200	[thread overview]
Message-ID: <20030410104506.7c4dc541.spider@gentoo.org> (raw)
In-Reply-To: <200304100413.03618.cedric@neopeak.com>

[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]

begin  quote
On Thu, 10 Apr 2003 04:13:03 -0400
Cedric Veilleux <cedric@neopeak.com> wrote:

> USE flags enabled in this package (only the ones relevant to the
> particuliar package)

already there, tagged at the end of a .tbz2

<cut> 

> Then a binary enabled portage would contact a master server and ask
> for a binary package compiled with the right combination of USE flags,
> profile and CHOST and if it exists download it and install it, and if
> it does not compile it from the sources..

unfortunately this requires a loot of computing and storage on the
server, as well as bandwidth.   That why I suggested a set of simple
defaults, people who go beyond that, go for source.   We really 
shouldnt spend the energy on "fixing" another set of binary package
management when others have done that for us already. (dpkg, rpm, slack,
bsd)

The GRP are a nice step,  and works well, if we could make it a bit more
usable than current.  I dont advocate going for a lot of hoops and
developertime to make a binary distro as smooth as Gentoo is from
source, since it wouldnt ever be maintained in the same way.   I do
however advocate that GRP become easier to use by default. 


//Spider




-- 
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-10  8:45 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 [this message]
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=20030410104506.7c4dc541.spider@gentoo.org \
    --to=spider@gentoo.org \
    --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