For the non-stripping bug, maybe we can avoid recompilation to achieve our goal of stripping.
What do we want?
In v0.4.3 (the next stable release of Hyperbola/GNU Linux-libre), all binaries and libraries in our packages should be stripped as desired.
Where dose the next stable release come from?
The current testing release.
What is the current testing release?
Many packages which are consist of binaries, libraries and some other files.
So what can we do?
Decompress those packages, strip files if needed, modify the corresponding metafiles, then repackage and update the signatures.
Next copy the current testing release to the next stable release.
Finally update core.db and extra.db.
Details are as follows. (For example, consider the package grep.)
Step 1. $ bsdtar -xf https://repo.hyperbola.info:50011/gnu-p … pkg.tar.lz
Step 2. $ strip -s pkg/grep/bin/grep
Step 3. Compute the new hashes of pkg/grep/bin/grep as below.
$ md5sum pkg/grep/bin/grep | cut -d ' ' -f 1 (The result is 3624a90a6e7ca3f512f6ab26839693e5)
$ sha256sum pkg/grep/bin/grep | cut -d ' ' -f 1 (The result is 1f826712974232b4483b2b995797bbf36bce193ef5073fb0f98652a240c299cc)
$ cat .MTREE | gzip -d > .MTREE.txt
Find the line "./bin/grep time=1626931654.540085000 size=184488 md5digest=8c7677260483563dce72662577f242cb sha256digest=00e8b6b117d138ddec316a0b09b4a5fa901ae8cde32d1a4fa8f6550bbc94bbb9" in .MTREE.txt
Update this line. (The new line is "./bin/grep time=1626931654.540085000 size=157824 md5digest=3624a90a6e7ca3f512f6ab26839693e5 sha256digest=1f826712974232b4483b2b995797bbf36bce193ef5073fb0f98652a240c299cc".)
$ cat .MTREE.txt | gzip -9 > .MTREE
Step 4. Modify .PKGINFO
Only the line "size = 1173504" needs to be modified.
Step 5. Repackage (use bsdtar directly rather than `makepkg -R`) and update the signatures.
The above procedure is just for a single package.
But we can write a shell script to implement the similar procedure for all packages.
Certainly, the develop team needs some time to discuss and to implement the code.
What's the advantqages of this idea?
1. All modifies happens on the side of the develop team.
2. No recompilation is needed. (I guess one day is enough for fixing all packages if the performance of Hyperbola's server is strong.)
3. Complete automation. (The only human time consumption is from implementing the shell script.)
Note.
1. Please do more tests on the shell script before the final fix to avoid importing new bugs.
2. Don't forget to update core.db and extra.db.
3. The develop team should first finish the fix of all packages, and then generate the new live ISO hyperbola-milky-way-v0.4.3-dual.iso. Otherwise, the live ISO will be still "non-stripped". If my estimation is correct, the size of the desired hyperbola-milky-way-v0.4.3-dual.iso is less than 700MB.