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 C8D9C1381F3 for ; Sat, 15 Jun 2013 15:24:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4360BE096D; Sat, 15 Jun 2013 15:24:36 +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 5C8B6E0966 for ; Sat, 15 Jun 2013 15:24:35 +0000 (UTC) Received: from [192.168.1.210] (S010600222de111ff.vc.shawcable.net [96.49.5.156]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: dolsen) by smtp.gentoo.org (Postfix) with ESMTPSA id 6E20233E3A6; Sat, 15 Jun 2013 15:24:34 +0000 (UTC) Message-ID: <1371309858.28535.30.camel@big_daddy.dol-sen.ca> Subject: Re: [gentoo-dev] [RFC] SRC_URI behaviour From: Brian Dolbec To: gentoo-dev@lists.gentoo.org Cc: mva@mva.name Date: Sat, 15 Jun 2013 08:24:18 -0700 In-Reply-To: <20130615150549.5faa3829@gentoo.org> References: <51BC2C55.7010506@mva.name> <20130615150549.5faa3829@gentoo.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.6.4 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 Content-Transfer-Encoding: 8bit X-Archives-Salt: 4e69f5d0-0a4d-4e36-935a-cc2eeb3fdead X-Archives-Hash: c8e659b781d1a271bd4a7208946ca844 On Sat, 2013-06-15 at 15:05 +0200, 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. > Well, there is an app in gentoo that can already handle every VCS type. It could easily be modified to handle the above syntax. The portage mods would also not be difficult to interface to it. The BAD!!! part is that it would require even more time for portage to sort out the VCS deps that would need to be added to it's dep calculations after checking the SRC_URI. GOD!, it's already getting slower than it was many years ago before Brian's pkgcore optimizations began to be applied. Not to mention GB's of memory and multiple cores now available that wasn't those many years ago... The other thing is that would put a mandatory system requirement on layman which many of the devs would be opposed to. But, there is an open bug calling for it to be merged with portage... > 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. > also, agreed