public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dan Armak <danarmak@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Binary release of gentoo
Date: Fri, 11 Apr 2003 17:42:30 +0300	[thread overview]
Message-ID: <200304111742.30377.danarmak@gentoo.org> (raw)
In-Reply-To: <20030410160128.2d62a75c.xwred1@xwredwing.net>

[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 2134 bytes --]

On Friday 11 April 2003 02:01, Matt Thrailkill wrote:
> > Besides building against GRP would mean a) maintaining a grp chroot 
> > (reasonable) and b) building every package twice - once for myself, once 
for 
> > grp. (No ccache because my cflags are different from grp's). So twice the 
> > build time. Ugh.
> 
> Curious though, how much time is spent trying to build such and such an 
ebuild until you actually get it right and then finally compile something 
that works and installs fine on your box?

Well ok, 'twice' isn't accurate. But it still does mean another full build of 
everything I commit, which is a lot by the same calculation that says it 
would take dedicated server(s) to do this. And we don't all have server-class 
development machines at home. The remote developers'-build-server is much 
better.

> Do you think the onus is more on finding machines to compile it all with or 
machines to host it all with?  I would think that some hotrodder overclocker 
types, the kind that run Gentoo cause they like watching gcc scrolling in an 
xterm, would be able to get an impressive distcc farm built out of the boxes 
they personally own.  Ibiblio probably wouldn't be happy hosting binaries 
though.

The hotrodders are ruled out for the same reason a p2p network is - we 
wouldn't be able to trust them (maybe a few we know, but not just anyone who 
has gentoo and a fast box). We need a server we can control and make sure is 
secure.

If we have a lot of uptodate GRP packages, usage will spread very very rapidly 
and downloads will rival or perhaps pass distfile downloads (remember that 
only a part of the latter goes through our mirrors, some still download from 
packages' homesites). So even if all our existing mirrors ageed to host this 
too, it would more than double the bandwidth we'd use up. It would also 
multiply many times the amount of spaec we take on a mirror, because every 
package would exist for a geat many archs.


-- 
Dan Armak
Gentoo Linux developer (KDE)
Matan, Israel
Public GPG key: http://cvs.gentoo.org/~danarmak/danarmak-gpg-public.key

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

  parent reply	other threads:[~2003-04-11 14:42 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
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 [this message]
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=200304111742.30377.danarmak@gentoo.org \
    --to=danarmak@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