On Fri, 2017-03-31 at 19:40 +0200, Oleksij Rempel wrote: > Am 31.03.2017 um 19:17 schrieb Ben Hutchings: > > On Fri, 2017-03-31 at 18:52 +0200, Oleksij Rempel wrote: > > [..] > > > I don't think it makes any sense. Why should we symlink some thing > > > different/not_stable to file name of stable firmware? > > > Especially if we have 1.dev.0? > > > firmware-ath9k-htc package should and can provide any latest possible > > > version of firmware form git. All possible distribution patches are > > > welcome as well. > > > firmware-ath9k-htc-v1.5 should provide stable version without any > > > chanes. This is needed to make sure suers are able to fall back to > > > working version of firmware even if firmware-ath9k-htc will brake > > > connection. > > > > If this package is not going to provide a stable ABI then I'll consider > > adding a Breaks instead. > > I'm not sure what you mean. Firmware filenames are supposed to indicate ABI versions. Just like shared library sonames. Just like kernel module directory names. You've told me that you're not going to do this. So it sounds like the kernel will need to have something like 'Breaks: firmware-ath9k-htc (>= 1.5~)'. Ben. -- Ben Hutchings To err is human; to really foul things up requires a computer.
Attachment:
signature.asc
Description: This is a digitally signed message part