On Sunday, 1 March 2020 17:40:59 GMT Colin Watson wrote: > Thanks, but this is unlikely to be a very helpful approach for files > built as part of distribution-managed packages, where the shipped files > are normally expected to be immutable (for example, checksumming the > installed files would fail after doing that kind of thing). > > It would be preferable to make the download file independent of the > ghostscript version, if possible. If that isn't possible, I'll need to > figure out some way to annotate the implied dependency in my packages' > metadata, in order that we can know when we need to rebuild groff.
Is the download file expected to be immutable? There are instructions how to add fonts to groff, which involves changing the download file. How do packagers deal with configuration files which are intended to be editable by users? Cheers Deri
