Search Linux Wireless

Re: Firmware versioning best practices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > Don't put the version into the filename. This is not a common
> > practice for Linux / BSD / whatever systems. Usually you have
> > a "kmail" file, not a kmail3.5, kmail4.0 and kmail4.2 file.
> 
> I think in this context libyyy.so.x.y.z is better analogy.
> firmware is not an executable What is the reasoning behind this
> common practice? 

There's no version of the library in the file-name, but the 
version of the API. So if the API changes, and might break users 
of the API, you increase the filename.

But you won't have a libc-2.3.6.so file. Instead you have a 
package "libc6_2.3.6.ds1-13etch9_i386.deb" which contains the 
file libc.so.6.

-- 
http://www.holgerschurig.de
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux