Very much appreciate the feedback. Willing to learn, but overwhelmed by the Debian machinery.
Stupid question at the top: If I dput another package, does it update this one or do I need to delete the currently uploaded package from mentors first?
- d/changelog. A lot has changed. Here are pointers to 'brief' change logs for 2.7, 2.9, and 2.10:
That's four years of why to retrace, and the actual check-in messages from the repository would be much longer. Does Debian really want all of that?
- d/patches
- Not sure what a dep3 header is, yet. More to learn.
- All but one of the patches is checked-in upstream already.
- I don't know how to have config.guess be updated at build time? Did not know about that one. Is this part of automake? TinyMUX is more autoconf than it once was, but it still doesn't use automake or libtool.
- Dependency-created-noise.patch. The way users normally build TinyMUX is untar the package, ./configure;make depend;make. The 'make depend' scans all the include files and builds ".depend" which is then re-consumed by Makefile. It must exist -- at least empty. The Debian build system would see either way as a source change, but it isn't a change to taken upstream. It always changes in different ways in every environment.
- d/copyright dep5...OK, more to study. The copyright is the same as previous 2.6 package except for the dates. That was hammered out between the four MUSH flavors (PennMUSH, TInyMUSH, TinyMUX, and RhostMUSH). I'm loath to change the substance of it, but if there is some Debian-friendly form to call out that it is the Artistic license, that seems reasonable enough.
- silent rule. TinyMUX uses the other autoconf tools, but not libool or automake. Silent rule seems to be a term from those things?
- d/rules. I'm picking this up from the previous maintainer, Noltar, and there should be simpler ways of doing this now. I'm just not up to speed on them and haven't found examples I grok, yet. I want to use the simple debhelper method. dh, done.
Stephen