From: Michael Weber <xmw@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] SRC_URI behaviour
Date: Sat, 15 Jun 2013 23:31:35 +0200 [thread overview]
Message-ID: <51BCDD37.7000709@gentoo.org> (raw)
In-Reply-To: <51BC847A.6050109@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 06/15/2013 05:12 PM, Rick "Zero_Chaos" Farina wrote:
> There is currently no need for improvement in my eyes, and I'm not
> sure this could be considered improvement anyway.
i.e. git-2.eclass provides support for environment override (and
variables) for branches, commits and repos, for example
EGIT_REPO_URI=<some other fancy git clone>
Hard to cover/encode this functionality in your proposed urls.
These look - by the way - a lot like the "new" packer-4.something git
url in Archlinux/AUR.
"our" VCS eclasses should still be superior in functionality.
++ for global RESTRICT="fetch|mirror" with overrides in both ways on
per url basis as prefix to the protocol, like nomirror+http:// and
fetch+git:// . But this needs tivial (?) adaption in every VCS eclass.
- --
Michael Weber
Gentoo Developer
web: https://xmw.de/
mailto: Michael Weber <xmw@gentoo.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.20 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iF4EAREIAAYFAlG83TcACgkQknrdDGLu8JAq/wEAmUQkeQaLY8FVGZpO9YNShR43
DQ4hrgT1TNSnUQcwzZQBAImK9nurCVcUn4LJSBD0mtCQah2VVo1VfTUzeoMJs1Tt
=B9vk
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-06-15 21:31 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
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 [this message]
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=51BCDD37.7000709@gentoo.org \
--to=xmw@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