On 14/11/2012 13:43, Philip Ashmore wrote: > Hi there. > > As someone who develops software for Debian I encounter situations where I have > to specify the same information multiple times, and when that information > changes I have to remember to update it in each of these places. > > Just now I had to add a debian/*doc.postrm.in to one of my projects. > Makefile.am - save the *in file in EXTRA_DIST > configure.ac - convert the *.in to a *. Why are you generating debian/* files from within the upstream build system? That's just wrong. Packaging is packaging. Upstream matter is upstream matter. Also, you don't need to add the file into EXTRA_DIST if you've already added it using AC_CONFIG_FILES -- autotools does that automatically. > Git - add to version control. Ack. > makefile - new version If you generate your upstream tarball with autogen/make dist, you should never have this issue. > NEWS - what's changed > ChangeLog - what's changed Autogenerate this from git log. Some upstreams don't bother with this, even. > Git - store the changes Ack. As you can see, you're uselessly repeating steps that can already be automatically done today, in addition to doing it just plain wrong (re: Makefile.am/configure.ac) > [...] That aside, I have nfc how to interpret your proposed text file thing, but GNOME has something similar, called DOAP files[1], which albeit in XML format, are more readable than yours. (And finally, like Ben said, please don't ask anyone to package anything in this format.) [1] https://live.gnome.org/MaintainersCorner#maintainers -- Kind regards, Loong Jin
Attachment:
signature.asc
Description: OpenPGP digital signature