Am Samstag, 12. Mai 2018, 15:47:57 CEST schrieb Rich Freeman:
> On Sat, May 12, 2018 at 8:20 AM Gerion Entrup <gerion.ent...@flump.de>
> wrote:
>
>
> > Different version keywording can be done as before:
> > ```
> > if [[ ${PV} == "3.1" ]] ; then
> > KEYWORDS="~amd64 ~x86"
> > else
> > KEYWORDS="amd64 x86"
> > fi
> > ```
>
> From a readability standpoint I could see this getting out of hand if we
> aren't careful.
I have kind of copied this code from a package, where a 9999 ebuild exists. So
it is already there.> Also, we'd want to keep this simple enough that the simple > act of stabilizing a package doesn't introduce regressions (perhaps even in > versions that we don't intend to touch). We'd also need rules about > conditionals so that the metadata cache works. Maybe this rule can be added: 4. Stable ebuilds are never multiversioned. So once an ebuild get stable it is split out of the multiversion ebuild (aka copied) and not touched anymore. Maybe this rule can be smoothed by moving the split to the point where new features are introduced in the ebuild: 4. If a multiversion ebuild contains a stable version and is changed featurewise (e.g. a new useflag), then the stable version is split out of the multiversion ebuild. I don't know the internals of the metadata cache, so I can't say something to that. > You also would need to be careful about ebuild revisions in general, since > you're potentially affecting multiple versions at the same time. You are right. But maybe it's the same fix, that is applied to all versions at once. > How would revbumps fit into this? All kinds of bad things can happen by > editing ebuilds in place, and this would compound the issue. Maybe it is possible to solve with the following method: 1. If the fix affects all ebuild versions, revbump all versions in the ebuild. 2. If the fix affects only one version, split out this version of the ebuild and make it an explicit one (together with the fix). The thing is that it is an additional concept. It does not replace the current mechanisms and at best reduces overhead for ebuilds that are identical. Gerion
signature.asc
Description: This is a digitally signed message part.
