Re: [gentoo-dev] [RFC] multiversion ebuilds

[Mathy Vanvoorden <mathy@vanvoorden.be>]

[-- Attachment #1: Type: text/plain, Size: 1163 bytes --]

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

It would result in the same outcome but it seems to me that a lot less work
(almost none?) is needed to implement it.

Benefits compared to your suggestion:
* you don't need to add the extra VERSIONS variable and related logic
* you don't need the set of rules
* you can have multiple multiversioned ebuilds per package

I'm not sure if adding the foobar-1.x file is allowed by portage.

You would still need logic like this for the keywording:

```
> if [[ ${PV} == "3.1" ]] ; then
>         KEYWORDS="~amd64 ~x86"
> else
>         KEYWORDS="amd64 x86"
> fi
> ```
>

br,
Mathy

[-- Attachment #2: Type: text/html, Size: 1901 bytes --]