On Fri, Feb 01, 2019 at 11:40:59PM +0100, Christoph Anton Mitterer wrote: > On Fri, 2019-02-01 at 22:09 +0100, Marc Haber wrote: > > Generally I think it's good that the tool is gone,… updating code > > > should *always* be the task of the respective package management > > > system, cause otherwise it's not just easy that code-downloader- > > > > I violently disagree. We only release every two years. SSDs develop > > quickly. We should not ship a two year old file. > > If it's only that .h file that changes… it shouldn't be very difficult > to keep things up2date, or is it?
I don't think that having a new package version per stable point release just to update the data file is a real elegant way of using package maintainer and release team time. That's a classic case of volatile data that should either be in a dedicated package that can be built automatically and release much more often, or we could finally get in motion to trust upstream's distribution mechanism like we do for, for example, clamav. Greetings Marc jftr, clamav used to have an automatically built clamav-data package that contained daily updates, but that was killed off by the archive maintainers, refering people to the mechanisms offered by the package upstream. smartmontools is currently going the opposite direction.
