|
|
Subscribe / Log in / New account

Point releases for the GNU C Library

Point releases for the GNU C Library

Posted Oct 19, 2017 5:01 UTC (Thu) by wtarreau (subscriber, #51152)
Parent article: Point releases for the GNU C Library

There exists another option for maintenance versions, which usually satisfies everyone. The principle is to use the number of patches from the maintenance version as the patchlevel. What's nice with this method is that it's only increasing so it's easy to say "this CVE was fixed in 2.26.73" implying that anything above that has the fix as well, and there's no extra work as automated scripts can produce the tarball by simply using "git describe" followed by "git log | wc -l". I'm already using this in haproxy and that's very convenient for everyone including users.


to post comments

Point releases for the GNU C Library

Posted Oct 20, 2017 11:54 UTC (Fri) by nim-nim (subscriber, #34454) [Link]

Hi Willy,

Anyway the main problem is the lack of "release" notion at Git level, when devs want to use Git exclusively. One can try to workaround it but it will always be fragile and project-specific. I took the time to push the subject upstream.

https://public-inbox.org/git/1290947539.4254.150849603981...

I hope they'll do something.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds