Quoting Antoine Beaupré (2017-07-30 16:42:29) > > For documenting. The cron script already exists. ;) > I mean in /etc/cron.weekly for example.
But putting it there would enable it by default which I'd like to avoid. > > It even has documentation of how to use it at the top. What's missing is to > > somehow tell people that the script exists. > > Okay, so where can we do this - i suggested the wiki as a starting > point, but I guess adding it to the README file would be good as well? README.Debian would be a good place to reference that script. The wiki is a nice-to-have. All documentation should be inside the package itself. The wiki should only be a nice extra. > > Since it's not made to be used like a normal script (controlled via > > environment variables and redirections for logging) I don't think that > > would be a good idea. > It seems to have sane enough defaults that this shouldn't matter. I don't see > why that would be a problem anyways. I see the utility of having a script that just does the right thing. Especially because I guess that most people just run sbuild-update with the same options (-udcar) all the time anyways. But schroot is only the default chroot backend of sbuild. If we implement a method with as much visibility as putting into PATH now, then it should be future proof to also allow updating other sbuild backends. > Another advantage in having it in the PATH somewhere is that it could then > have a manpage and be cross-referenced from stuff like sbuild-update... > Autocompletion also does wonder for auto-discovery... sbuild-update could (and probably should) still reference to it even when it stays in /usr/share/doc
signature.asc
Description: signature
