>>>>> On Sun, 16 Jul 2023, Arthur Zamarin wrote: > Let me list some things as advantages to each one (since I see an > advantage to one as disadvantage to other).
> Advantages of field in metadata.xml:
> - local to package, easier to not miss. Easier to follow for the maintainer.
> - easier to find which group the current package relates to
> Advantages to group files:
> - easier to index (one file listing all children, instead of searching
> across repo who defines it)
> - easier to not repeat group. In the metadata field it might happen to
> repeat, less likely since it is easy to search, but similar group names
> might be created, merging them into one by mistake, or creating very
> similar names and mistaking them. When we have a single file, it is
> easier to see the whole picture and verify things.
> - since this is compressed information (special files instead of spread
> over repo), we could load all of them into app's cache, and make all
> computation easier.
> - enables an easier syntax as `pkgdev bugs @group1` to file a single bug
> for all of them. In Gnome's case as an example, we could have "gnome1",
> "gnome2", "gnome3", "gnome4", etc - groups standing for multiple
> "layers/stages" of stabilizing, and then you could just file `pkgdev
> bugs @gnome{1..4}` to file "at one click" the whole gnome stablereqs.
Can't we do the same that we do for local use flags? Namely, define them
in metadata.xml, but collect them in one central location?
Ulrich
signature.asc
Description: PGP signature
