From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id A83EE1381F3 for ; Sun, 16 Jun 2013 00:24:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 12996E0930; Sun, 16 Jun 2013 00:24:10 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 1AEEEE086B for ; Sun, 16 Jun 2013 00:24:09 +0000 (UTC) Received: from [192.168.26.7] (ip98-164-195-43.oc.oc.cox.net [98.164.195.43]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 3B9CF33E38D; Sun, 16 Jun 2013 00:24:08 +0000 (UTC) Message-ID: <51BD05A6.4090209@gentoo.org> Date: Sat, 15 Jun 2013 17:24:06 -0700 From: Zac Medico User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org, =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= Subject: Re: [gentoo-dev] [RFC] SRC_URI behaviour References: <51BC2C55.7010506@mva.name> <20130615150549.5faa3829@gentoo.org> In-Reply-To: <20130615150549.5faa3829@gentoo.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Archives-Salt: 0f4f32de-1597-46f9-af3e-d27d6987742f X-Archives-Hash: 18b876822bb573b278c76288dc806266 On 06/15/2013 06:05 AM, Michał Górny wrote: > Dnia 2013-06-15, o godz. 15:56:53 > "Vadim A. Misbakh-Soloviov" 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 -- Thanks, Zac