Dnia 2014-03-22, o godz. 15:33:27 Alec Warner <anta...@gentoo.org> napisał(a):
> https://wiki.gentoo.org/wiki/Package_Tags > > Object or forever hold your peace. Honestly, I don't think metadata.xml is a good place for it. While I like the consistency with general use of that file, I feel like it's going to make the application of tags more cumbersome, more noisy and make it harder to maintain consistency. As I see it, tags are not the same kind of package property as the description or package name. As I see it, current metadata.xml properties are somehow constant. They are usually set by the maintainer, do not change often and are strictly related only to the package. Tags, on the other hand, are more 'live'. They place the package somewhere in the 'global' tag hierarchy that can change over time. I expect that people other than maintainers will be adding tags to packages (and changing them), and that people will invent new tags and apply them to more packages. So, first of all, your solution would mean that every commit adding a new tag or changing one of the tags would modify the package metadata.xml. This means a Manifest update and a ChangeLog entry (please don't get into more rules for ChangeLogs now), and this means it will be harder to find actually useful entries there. So we make tag updates harder, and increase time and size of rsync. Secondly, since tags for every package will be held in different files, people will need dedicated tools to collect tags from all those files and add matching tags to their own packages. Long story short, we're going to have many 'duplicate' tags that will require even more commits with ChangeLog entries and Manifest updates. Worse than that, your GLEP doesn't even have any basic rules for naming tags -- like what language form to use and, say, which character to use instead of space. This sounds like the sort of things that's going to make it even harder to get some consistency, especially if some developers are going to follow someone else committing earlier and some will follow their own rules. I'd honestly prefer that -- if we should really keep tags in the tree -- to do that with a single 'metadata/tags' file or some kind of hierarchy there. Keep them outside the package directory -- bind packages to tags, rather than tags to packages. Keep all the commits in a single place without altering the ebuild work flow. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
