public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Rick \"Zero_Chaos\" Farina" <zerochaos@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] SRC_URI behaviour
Date: Sun, 16 Jun 2013 10:39:24 -0400	[thread overview]
Message-ID: <51BDCE1C.5000505@gentoo.org> (raw)
In-Reply-To: <51BD05A6.4090209@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 06/15/2013 08:24 PM, Zac Medico wrote:
> On 06/15/2013 06:05 AM, Michał Górny wrote:
>> Dnia 2013-06-15, o godz. 15:56:53
>> "Vadim A. Misbakh-Soloviov" <mva@mva.name> napisał(a):
>>
>>> 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
>>> "
>>
>> It simply can't work. Don't even try to implement, it's waste of time.
>> Just grep the tree, see how various packages use VCS-es. There's too
>> many differences, too many needs and -- most importantly -- VCS-es
>> change over time much more quickly than, say, unpackers.
>>
>> Even *if* we get a SRC_URI VCS support that works for all consumers,
>> and that'd be awfully hard to do properly, it will eventually stop
>> being 'good enough' and require further changes. It will just become
>> never-ending story for a minor benefit.
> 
> How about it we add a src_fetch phase, so that the VCS intricacies can
> be delegated to ebuilds/eclasses (like they are now, but without having
> to abuse src_unpack). If we include a way for src_fetch to communicate
> changes in VCS revisions to the package manager, then we'll be able to
> integrate functionality like smart-live-rebuild directly into the
> package manager (as discussed in bug 182028 [1]).
> 
> [1] http://bugs.gentoo.org/show_bug.cgi?id=182028

+1 on src_fetch in or out of the context of this thread.

+1 on more granular fetch/mirror restrictions

+-0 on VCS in SRC_URI, as I already stated I'm fine with the current
functionality (aside from a vast desire for src_fetch phase).

- -Zero
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRvc4cAAoJEKXdFCfdEflK990P/267Ej2p26SvRGItzFHtHakH
EwDEQcLxfykfqs1p1AWjR2O9e7ZvW7PaF9EyFdypY0MxAu0faB24ek4OKGD4842L
VbkQFXRjSOu1e+bLvQERofiVJ2/qSJZmg/phBsLwQiT0GVTm6ZXykZHSjfyTSALG
6ip+bhwUnYGGmxs8oudb7abBy7HfqhFlA6GTnyonqeRXre4QxfWFi1Yup/mRFuWp
XFwEoBe9t/95DBiXfjbvO5b6rlVEsChXuxELDUgP1dTdXTYKVRohs0lU6uZqlJkz
RY+8p8bJDsZas0Ucw7+7ePb93mH+XCKz5bvMrz2YhEM//NTOC6QY9+F6iy/NevTp
FNJeBCYUNKPpGzy4bm1649vDCqG51WK9iG8qtYO5G0y2QpkGZugUfALwalXK7L3M
eThjhlGrn0LZvGXxkYNtHgimFg3VWDJXJLHipMkP5dUqC5t4HEaEqgdGTCpzwuka
IUAahKdFLd3EZBlc3MHkYwuzfa0/MayOFiMcHKVV2+ONa5FcwkO8Rg6QJk5Xb7A1
NpPU87VampYERtaNcJKVACl8wR8Pltg4Y5xyz5Dgs+ga/gLvun6VePPO3WvKrAsS
UirS6VqysSEFaZTFotW0LAN6N8+Mll90gjRRgJxaQcGy1IiZ7VXYGzb8Q9nRWL9n
1PD6mk8hNr9C3aV14QzM
=7DTn
-----END PGP SIGNATURE-----


  parent reply	other threads:[~2013-06-16 14:37 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     ` Rick "Zero_Chaos" Farina [this message]
2013-06-15 15:12 ` [gentoo-dev] " 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=51BDCE1C.5000505@gentoo.org \
    --to=zerochaos@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