From: R0b0t1 <r030t1@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [RFC] multiversion ebuilds
Date: Tue, 15 May 2018 23:22:02 -0500 [thread overview]
Message-ID: <CAAD4mYiC8hRrjcH+CoTGCsKXT35DXUAeoE3qo3Um_M5bQHS-Bg@mail.gmail.com> (raw)
In-Reply-To: <pan$5cc94$78734776$1e7717ec$4946a59@cox.net>
On Tue, May 15, 2018 at 11:15 PM, Duncan <1i5t5.duncan@cox.net> wrote:
> Mathy Vanvoorden posted on Tue, 15 May 2018 11:32:30 +0200 as excerpted:
>
>> 2018-05-12 14:20 GMT+02:00 Gerion Entrup <gerion.entrup@flump.de>:
>>
>> 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.
>
Cygwin and MSYS(2) are currently mostly supported by Prefix, so using
symlinks might kill them as well. There is some kind of symlinking
support for NTFS now but it is very primitive.
Cheers,
R0b0t1
next prev parent reply other threads:[~2018-05-16 4:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 12:20 [gentoo-dev] [RFC] multiversion ebuilds Gerion Entrup
2018-05-12 13:47 ` Rich Freeman
2018-05-12 14:13 ` Gerion Entrup
2018-05-12 14:21 ` Ulrich Mueller
2018-05-12 14:36 ` Gerion Entrup
2018-05-12 15:23 ` Dennis Schridde
2018-05-12 14:24 ` R0b0t1
2018-05-12 14:38 ` Gerion Entrup
2018-05-12 19:49 ` Georgy Yakovlev
2018-05-15 9:32 ` Mathy Vanvoorden
2018-05-16 4:15 ` [gentoo-dev] " Duncan
2018-05-16 4:22 ` R0b0t1 [this message]
2018-05-16 6:15 ` Martin Vaeth
2018-05-16 6:26 ` [gentoo-dev] " Paweł Hajdan, Jr.
2018-05-16 6:46 ` Ulrich Mueller
2018-05-16 7:12 ` Ulrich Mueller
2018-05-16 7:38 ` Michał Górny
2018-05-16 23:33 ` R0b0t1
2018-05-17 15:44 ` Gerion Entrup
2018-05-17 16:16 ` Rich Freeman
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=CAAD4mYiC8hRrjcH+CoTGCsKXT35DXUAeoE3qo3Um_M5bQHS-Bg@mail.gmail.com \
--to=r030t1@gmail.com \
--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