From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [RFC] SRC_URI behaviour
Date: Sat, 15 Jun 2013 08:12:18 -0400 [thread overview]
Message-ID: <CAGfcS_knmiqLkooK2uEUt-aErhMMoA1XUWZTYVuJrn=sM6Jp2Q@mail.gmail.com> (raw)
In-Reply-To: <CAHcsgXQgRRN_X=WB3M6SzkubotfovmWg=guA5vte8Z9PAdudOw@mail.gmail.com>
On Sat, Jun 15, 2013 at 7:50 AM, Diego Elio Pettenò
<flameeyes@flameeyes.eu> wrote:
>
> On Sat, Jun 15, 2013 at 9:56 AM, Vadim A. Misbakh-Soloviov <mva@mva.name>
> wrote:
>>
>>
>> And, moreover, I guess, SRC_URI can even be used for VCS:
>>
>> SRC_URI="
>> git+ssh://github.com/lol/moo.git
>> hg+ssh://bitbucket.org/lol/moo
>> svn+ssh://assembla.com/lol/moo
>> "
>
> Over my dead CVS access.
Grandstanding aside, it is probably best to take this in chunks.
The all-or-nothing fetch restriction control does seem like a good
place to start improving. I could certainly see where that could
create needless problems. It just hasn't been much of an issue
because fetch restriction is rare. Mirror restriction is likely a
bigger problem even if it is somewhat user-invisible. Do we really
want to hammer something like dev.gentoo.org for patches that aren't
properly mirrored because the original source cannot be?
Rich
next prev parent reply other threads:[~2013-06-15 12:12 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-15 8:56 [gentoo-dev] [RFC] SRC_URI behaviour Vadim A. Misbakh-Soloviov
2013-06-15 11:50 ` Diego Elio Pettenò
2013-06-15 12:12 ` Rich Freeman [this message]
2013-06-15 12:14 ` Diego Elio Pettenò
2013-06-15 13:06 ` Rich Freeman
2013-06-15 13:15 ` Diego Elio Pettenò
2013-06-15 13:26 ` Andreas K. Huettel
2013-06-15 21:15 ` Michael Weber
2013-06-15 21:17 ` Diego Elio Pettenò
2013-06-15 21:19 ` Diego Elio Pettenò
2013-06-15 21:21 ` Michael Weber
2013-06-15 21:24 ` Markos Chandras
2013-06-15 21:40 ` Michael Weber
2013-06-15 21:25 ` Diego Elio Pettenò
2013-06-15 22:38 ` Rick "Zero_Chaos" Farina
2013-06-15 13:34 ` Ulrich Mueller
2013-06-15 13:37 ` Diego Elio Pettenò
2013-06-15 13:47 ` Ulrich Mueller
2013-06-15 13:57 ` [gentoo-dev] " Michael Palimaka
2013-06-15 13:59 ` [gentoo-dev] " Diego Elio Pettenò
2013-06-15 12:34 ` Vadim A. Misbakh-Soloviov
2013-06-15 13:50 ` Luca Barbato
2013-06-15 12:48 ` Alexander V Vershilov
2013-06-15 12:58 ` Diego Elio Pettenò
2013-06-15 14:22 ` Pacho Ramos
2013-06-15 13:05 ` Michał Górny
2013-06-15 13:11 ` Vadim A. Misbakh-Soloviov
2013-06-15 13:16 ` Diego Elio Pettenò
2013-06-15 15:24 ` Brian Dolbec
2013-06-15 15:33 ` Rich Freeman
2013-06-15 15:43 ` Luca Barbato
2013-06-15 15:51 ` Rich Freeman
2013-06-15 16:37 ` Ciaran McCreesh
2013-06-16 7:52 ` Arfrever Frehtes Taifersar Arahesis
2013-06-15 20:16 ` Anthony G. Basile
2013-06-16 0:24 ` Zac Medico
2013-06-16 11:46 ` Luca Barbato
2013-06-16 12:12 ` Georg Rudoy
2013-06-16 12:18 ` Vadim A. Misbakh-Soloviov
2013-06-16 13:41 ` [gentoo-dev] " Michael Palimaka
2013-06-16 14:39 ` [gentoo-dev] " Rick "Zero_Chaos" Farina
2013-06-15 15:12 ` Rick "Zero_Chaos" Farina
2013-06-15 21:31 ` Michael Weber
2013-06-15 16:35 ` Ciaran McCreesh
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='CAGfcS_knmiqLkooK2uEUt-aErhMMoA1XUWZTYVuJrn=sM6Jp2Q@mail.gmail.com' \
--to=rich0@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