glibc April 2018

glibc@lists.fedoraproject.org

2 participants
3 discussions

Source RPM size
by Florian Weimer 15 May '18

15 May '18

Would it concern you if the source RPM size grew to about 110 MiB? This data would not have to be uploaded with a “fedpkg new-sources” command for every upstream import, only once per Fedora release cycle. Thanks, Florian

2 14

tarballs vs ABI xml files in dist-git.
by Carlos O'Donell 14 May '18

14 May '18

Florian, You expressed some worry about checking in the tarballs for the frozen ABI specification into dist-git. Really git is not designed to hold tarballs, and the source cache is just wrong since this is not a source tarball (we used to abuse it also for the releng tarball). It is relatively easy to move all the files directly into dist-git, and use a lua construct like this: +%{lua: +-- List all of the frozen ABI xml files as source files. +function recursedir(directory) + local i, t, popen = 0, {}, io.popen + local pfile = popen('find "'..directory..'" -type f') + for filename in pfile:lines() do + i = i + 1 + t[i] = filename + end + pfile:close() + return t +end +# There are almost 2000 ABI specification files. +lines = recursedir ('releng/frozen-abi/') +-- Last Source file is numbered 12. +j = 12 +for i,v in ipairs(lines) do + print('Source'..i..': '..v) + j = j + 1 +end +} +%endif Which generates the source line entries from the directories. This would allow us to manually tweak the ABI files by hand and track the changes over time as we update glibc. Would this be a better design? -- Cheers, Carlos.

3 14

[PATCH] glibc.spec: Apply patches in logical order.
by Carlos O'Donell 19 Apr '18

19 Apr '18

The following commit removes the requirement for patches to be placed in 1000, 2000, or 3000 ID blocks depending on their upstream status. Instead upstream status is documented in the header of the patch with some semi-standard notation as described in template.patch. The patches are re-numbered and defined and applied in the same order. Verified that before and after the patch that the source tree does not change. The patch definition is resorted to match the patch application order. -- Cheers, Carlos.

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

glibc April 2018