public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Palimaka <kensington@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [RFC] SRC_URI behaviour
Date: Sun, 16 Jun 2013 23:41:54 +1000	[thread overview]
Message-ID: <kpkfat$kik$1@ger.gmane.org> (raw)
In-Reply-To: <51BD05A6.4090209@gentoo.org>

On 16/06/2013 10:24, Zac Medico wrote:
> 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

This sounds interesting. It definitely would be nice to have proper 
package manager support for VCS.

I don't think that this will somehow "legitimise" live ebuilds. We use 
policies to prevent inappropriate things from entering the tree, not by 
preventing tools that might facilitate it.

Best regards,
Michael



  parent reply	other threads:[~2013-06-16 13:42 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     ` Michael Palimaka [this message]
2013-06-16 14:39     ` 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='kpkfat$kik$1@ger.gmane.org' \
    --to=kensington@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