public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaranm@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 22:20:06 +0100	[thread overview]
Message-ID: <20050505222006.736bf1c7@snowdrop> (raw)
In-Reply-To: <20050505210420.GA20866@curie-int.orbis-terrarum.net>

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

On Thu, 5 May 2005 14:04:20 -0700 "Robin H. Johnson"
<robbat2@gentoo.org> wrote:
| I've tried to dig through our policy documents, to find the policy
| regarding RESTRICT=mirror/fetch. I don't find anything in the htdocs
| tree from CVS, beyond a few brief mentions in the handbook.

Some of it's in the "not policy" documents:

http://www.firedrop.org.uk/devmanual/general-concepts/mirrors/

Contributions welcomed if someone knows exactly what the rules are :)

| RESTRICT=[no]mirror
| -------------------
| - Files too large for the mirrors? (What is the size limit?)
| - License issues?
| - anything else?

AFAIK it's now just licence issues.

| 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.

Now that primaryuri exists, yes. That's a fairly recent feature,
however.

-- 
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail            : ciaranm at gentoo.org
Web             : http://dev.gentoo.org/~ciaranm


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

  reply	other threads:[~2005-05-05 21:16 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 [this message]
2005-05-05 21:30 ` Corey Shields
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=20050505222006.736bf1c7@snowdrop \
    --to=ciaranm@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