public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul de Vrieze <pauldv@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Feature request
Date: Thu, 1 Jan 2004 21:24:34 +0100	[thread overview]
Message-ID: <200401012124.34815.pauldv@gentoo.org> (raw)
In-Reply-To: <1072988075.16658.18.camel@Star.BerthoudWireless.net>

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

On Thursday 01 January 2004 21:14, Scott Taylor wrote:
> Whatever came of comment #14 of bug 28806 - That is something along the
> lines of what i'd like to see. In my own network, I have a central
> server with its /usr/portage/distfiles available locally by anonymous
> ftp. This way, my local mirror has any file used on itself (or
> prefetched for my other workstations by way of an emerge --fetchonly).
> So, I do have files on this machine that should be checked first,
> regardless of whether a build is marked "nomirror". For any network that
> has local repositories either ftp/nfs/samba/whatever could find that
> useful too. Lists of other groups of mirrors (sourceforge, etc) are also
> good things to allow customization on. Its just my luck to want some
> huge source that it tries to get from a slow sourceforge mirror on the
> other side of the world...

A stopgap that you could use is to install squid on the server node. Use it as 
a emerge only proxy. However you MUST make some config changes. Change the 
used real memory to a low value as it will not have any point for portage 
(you'll not download things again and again), but REALLY REALLY IMPORTANT
is to set the 

maximum size of cached items

to something that is in the 100 or even 200 mb range. (Standard is 1 mb or 
something like that, quite pointless for portage). If you give your caching 
proxy enough cache space it will be quite effective, and it even saves you 
maintaining the distfiles dir. It also stops the need for different schemes 
for allowing distfile requests from any host to get onto the master cache.

Paul

-- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@gentoo.org
Homepage: http://www.devrieze.net

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

  reply	other threads:[~2004-01-01 20:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1AbhRM-0007Ja-C9@smtp.gentoo.org>
2004-01-01 19:54 ` [gentoo-portage-dev] Feature request Paul de Vrieze
2004-01-01 20:14   ` Scott Taylor
2004-01-01 20:24     ` Paul de Vrieze [this message]
2004-01-01 20:43       ` Scott Taylor
2004-01-01 21:19         ` Paul de Vrieze
2004-01-01 21:43           ` Scott Taylor
2004-01-02  5:08     ` Brian
     [not found] <E1AbhRH-0004kq-Lq@smtp.gentoo.org>
2004-01-02 20:20 ` Marius Mauch
2003-12-31 14:34 Allen Parker

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=200401012124.34815.pauldv@gentoo.org \
    --to=pauldv@gentoo.org \
    --cc=gentoo-portage-dev@lists.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