public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Corey Shields <cshields@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Policy on RESTRICT=[no]mirror and use of mirror://foo/
Date: Thu, 5 May 2005 14:30:18 -0700	[thread overview]
Message-ID: <200505051430.18082.cshields@gentoo.org> (raw)
In-Reply-To: <20050505210420.GA20866@curie-int.orbis-terrarum.net>

On Thursday 05 May 2005 02:04 pm, Robin H. Johnson wrote:
> Unless there is something I've missed, why do we have ebuilds with
> RESTRICT=nomirror, having a GPL-2 license, and distributed via
> sourceforge? Wouldn't RESTRICT=primaryuri be much better? Most fetches
> would go to SF first, and we'd still have a copy available on our
> mirrors.

At one point in time someone suggested that we may as well utilize other 
people's mirror networks that are already out there, rather than our own.  
This then got implemented for stuff like sourceforge packages.

Unfortunately this plays hell for lots of people.  If you have a local mirror, 
then you get files fast and without using your outside bandwidth.  Having to 
wait for a file from some mirror in zimbabwe because "that package already 
has a mirror structure" defeats the purpose of running a local mirror.

On top of that, if you have a private network (RFC 1918) with a gentoo mirror 
on the inside, you can't reach the SRC_URI on restrict=nomirror packages, and 
they don't end up on the mirror anyway.  We had this problem on dozens of 
servers at IU..  At one point in time even gentoo-sources was marked 
nomirror, since kernel.org had their own network.

I think that nomirror should be used as seldom as possible.  Licensing issues 
are legit.  We've had one case where mirror admins complained about a file 
that was too big (a 2 gig neverwinter nights file), but otherwise I have 
talked with them before about releasing "nomirror" wherever we can, and they 
didn't mind.

If someone wants to put the "Official" stamp on the licensing/nomirror policy, 
that would be great.  Just as important, I think we need to backtrack and 
clear out that restriction wherever it is unnecessarily used.

Cheers,

-C

-- 
Corey Shields
Gentoo Linux Infrastructure Team and Devrel Team
Gentoo Foundation Board of Trustees
http://www.gentoo.org/~cshields
-- 
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-05-05 21:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-05 21:04 [gentoo-dev] Policy on RESTRICT=[no]mirror and use of mirror://foo/ Robin H. Johnson
2005-05-05 21:20 ` Ciaran McCreesh
2005-05-05 21:30 ` Corey Shields [this message]
2005-05-06  4:37   ` Alin Nastac
2005-05-06  5:53     ` Robin H. Johnson
2005-05-06  6:06       ` Brian Harring
2005-05-06 21:08   ` Chris Gianelloni
2005-05-07 16:42     ` Lance Albertson
2005-05-05 22:01 ` Mike Frysinger
2005-05-05 22:06   ` Lance Albertson
2005-05-05 22:21     ` Corey Shields
2005-05-05 22:22       ` Lance Albertson

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=200505051430.18082.cshields@gentoo.org \
    --to=cshields@gentoo.org \
    --cc=gentoo-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