W dniu wto, 09.01.2018 o godzinie 11∶15 -0500, użytkownik Alec Warner napisał: > On Tue, Jan 9, 2018 at 10:11 AM, Alec Warner <anta...@gentoo.org> wrote: > > > > > On Tue, Jan 9, 2018 at 9:43 AM, Michał Górny <mgo...@gentoo.org> wrote: > > > > > Add @MAINTAINER comments before each profile set indicating > > > the effective maintainer for the following set of profiles. While most > > > of those entries may seem obvious at first, I expect that some > > > of the sub-profiles will eventually 'change hands', e.g. the /hardened > > > sub-profiles would be maintained by Hardened, etc. > > > > > > The main goal is to provide a clear indication of who maintains each > > > profile. This will be of great help both to bug-wranglers (who currently > > > have to pretty much guess who to assign profile bugs to) and to other > > > developers who plan to commit larger changes and want to get ACK from > > > appropriate parties. > > > --- > > > profiles/profiles.desc | 23 +++++++++++++++++++++++ > > > 1 file changed, 23 insertions(+) > > > > > > diff --git a/profiles/profiles.desc b/profiles/profiles.desc > > > index 66dd7a32799f..8c9bd78143a1 100644 > > > --- a/profiles/profiles.desc > > > +++ b/profiles/profiles.desc > > > @@ -7,6 +7,7 @@ > > > #arch profile_directory status > > > > > > # Alpha Profiles > > > > > > How are machines supposed to read this data? > > Can we consider structured data? > > > > Sorry using more words: > > Currently the data is 'structured' in that its space separated data; and > you can probably use basic csv parsers to get at it (but not comments.) Now > we are adding a maintainer field. But its in a comment (so machines can't > read it). So how will machines read this data; or just make an explicit > goal that machines shouldn't. >
Similar to eclassdoc. Grep for @MAINTAINER comment preceding the profile, read the line and grab e-mail address(es). This is a non-obligatory extension. We can't change the file format without breaking existing tools. Comments are safe. -- Best regards, Michał Górny
