On Wed, 2020-09-16 at 08:18 +0200, Ulrich Mueller wrote: > > > > > > On Wed, 16 Sep 2020, Michał Górny wrote: > > > +- one or more ``<version/>`` elements, each containing a version > > + constraint in the format matching EAPI 0 dependency specification > > + with the package category and name parts omitted, e.g. ``<1.7``. > > That's not a very powerful syntax, so unless I miss something, > metadata.xml would have to be updated for almost every stable candidate. > > To give an example, released versions of app-editors/emacs have exactly > two numerical components, while prereleases and release candidates have > three components or are marked _rc. Both would be impossible to match > with the proposed syntax.
It's not 'one size fits all'. It will work for a number of packages, e.g. XFCE without too frequent updates. In the end, it's primarily designed around 'silencing' StableRequest results once they are reported, i.e. for packages that have long-ish RC periods. > So IMHO this has no advantage over keeping the information in the ebuild > (e.g. as a PROPERTIES token). > It has two advantages: 1. It reduces the risk of accidentally leaving it in the stable ebuild. 2. It handles specifying multiple stabilization candidates on different branches. I don't see how ebuilds would do that. -- Best regards, Michał Górny
signature.asc
Description: This is a digitally signed message part
