Dagobert Michelsen <[email protected]> writes: > Hi Peter, > > Am 12.04.2013 um 20:45 schrieb Peter FELECAN: >> Yann Rouillard <[email protected]> writes: >>> http://packages.debian.org/unstable/database/mysql-server-5.5 >>>> >>>> ...it lists multiple maintainers. For a package such as MySQL, it >>>> makes complete sense. I don't know the internals, but I'm pretty sure >>>> that the list of maintainer is kept as a separate entity from the >>>> changelog. >>> >>> >>> The maintainers's information is located in the debian/control file, in the >>> source package. >> >> Our "control" file is the recipe, i.e., the Makefile. Having a variable >> containing a list of maintainers seems to be a nice addition. What Dag >> thinks about this? > > I am ok with this. > MAINTAINED_BY += pfelecan > MAINTAINED_BY += dam > > How would a workflow look like?
In the pkginfo file we have this: VENDOR=http://leocad.googlecode.com/files/ packaged for CSW by Peter Felecan [email protected] We should have: VENDOR=http://leocad.googlecode.com/files/ [email protected] ... OPENCSW_MAINTAINERS=Peter Felecan, Dagobert Michelsen The last variable contain the values of the multi-valuated attribute "maintainer". The user uploading the package is the value of the attribute "NMU" --- when I'm writing about "attribute" I'm thinking to the packages database schema. The variable in the pkginfo file is generated at packaging time. The attributes are valuated at upload time. Does it seems reasonable? What thinks our data-base czar but not less enlightened colleague? :-) -- Peter _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
