Bug#968000: libconfig-model-dpkg-perl: Get policy release dates in another way
Russ Allbery
rra at debian.org
Sat Aug 8 01:14:30 BST 2020
gregor herrmann <gregoa at debian.org> writes:
> Right, except that this also doesn't work at build time.
> But if we skip the test phase that would be ok.
> What I'm wondering is:
> - depending on debian-policy would be another dependency, and the
> debian-policy only installs files to /usr/share/doc which is not
> guaranteed to exist; and there's also no easily parsable file there;
> - will lintian continue to ship
> /usr/share/lintian/data/standards-version/release-dates ? Then we
> could still parse it ourselves without the Lintian perl modules;
> - even if lintian ships the perl modules in a private path, it would
> be possible to use it; if this makes sense depends on the reason
> why lintian moves the files, which I haven't fully understood yet
> (my impression is more that this has to do with lintian internales
> like tests that with the question if the modules should be uses by
> others).
> But yeah, maybe just using rmadison or whatever other online method
> to get the lates S-V is easier than to rely on lintian.
If it would be helpful for debian-policy to ship this information directly
in the package, that should be relatively easy to do. Feel free to open a
bug against debian-policy. I'm not sure if Sean would see any problems
that I'm not seeing, but I personally have no objection to Policy starting
to install some machine-readable information about Policy in files in
/usr/share/debian-policy in a documented format.
If we did that, I would probably ship this information in YAML rather than
in the somewhat ad hoc format of Lintian's data file (which was my fault
originally).
--
Russ Allbery (rra at debian.org) <https://www.eyrie.org/~eagle/>
More information about the pkg-perl-maintainers
mailing list