From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 836CD1382C5 for ; Wed, 16 May 2018 04:17:51 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C0E4DE0901; Wed, 16 May 2018 04:17:44 +0000 (UTC) Received: from blaine.gmane.org (unknown [195.159.176.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 5FEF4E08E2 for ; Wed, 16 May 2018 04:17:44 +0000 (UTC) Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1fInqc-0002ro-Cq for gentoo-dev@lists.gentoo.org; Wed, 16 May 2018 06:15:30 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: [RFC] multiversion ebuilds Date: Wed, 16 May 2018 04:15:23 +0000 (UTC) Message-ID: References: <2532421.f3YmpD0exa@gump> 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-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@blaine.gmane.org User-Agent: Pan/0.145 (Duplicitous mercenary valetism; 5f69c29ad) X-Archives-Salt: 49c16fa4-486d-448f-974b-3fecb35a1d15 X-Archives-Hash: 92c3913497a11ac82e27f55237229f07 Mathy Vanvoorden posted on Tue, 15 May 2018 11:32:30 +0200 as excerpted: > 2018-05-12 14:20 GMT+02:00 Gerion Entrup : > > just an idea for now. But what you think about multiversion ebuilds? >> Technically this could be realized with the following line in the ebuild >> itself: >> ``` >> VERSIONS=( 3.0.11 3.0.12 3.1 ) >> ``` >> > > I like the idea of multiversion ebuilds but why would you complicate the > process by putting it in a variable? Why not just use symlinks and have the > following: > > foobar/foobar-1.x > foobar/foobar-1.1.ebuild -> foobar-1.x > foobar/foobar-1.2.ebuild -> foobar-1.x > foobar/foobar-2.x > foobar/foobar-2.1.ebuild -> foobar-2.x AFAIK symlinks aren't allowed in the gentoo tree, with the given reason being that some users, particularly those with limited net access and thus "sneakernetting" from where they /do/ have net access, may place the tree on or transfer it via no-symlink-support FAT32 or similar, perhaps downloading it from an MS machine or the like. Of course users may use symlinks on their own copies, but they're not allowed in the official tree. Tho perhaps that can be reevaluated. But while there's more connectivity now than over a decade ago when that policy was created, I expect there's still those paying by the meg or gig for net access locally, that won't enjoy having their sneakernet sync routine disrupted. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman