-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Wed, 27 Mar 2019, Allan McRae wrote:
On 27/3/19 7:20 am, Erich Eckner wrote:
https://mirror.pkgbuild.com/core/os/x86_64/core.links.tar.gz
It contains (as far as I can tell) the names and versions of libraries against which binaries in a package are linked.
This is not a repo, so should not be managed by repo-add.
Thanks for your answer, but: Is the *.files.tar.gz a "repo"? My interpretaion (so far) was, that the *.files.tar.gz and *.links.tar.gz files are caches for search accellerations inside the repo (the first for "who owns that file" and the second for "who links against that file") - is this not the case? Also note, that managing the *.links.tar.gz file with repo-add would have benefits from a cleanness point of view: currently it's created asynchronously but it could be created synchronously (e.g. *.db.tar.gz, *.files.tar.gz and *.links.tar.gz would be always in-sync). Furthermore, each downstream distribution wanting to have sogrep needs to implement the createlinks script asynchronously, too. This would become obsolete if it was part of repo-add. Cheers, Erich -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAlyanM0ACgkQCu7JB1Xa e1pZXxAAuCHROvweoz1+hHngXF9rCQcd3s8wAI8VmWJ+8goplAiZG3WVf5k5V/Ua 1hVE7dR609hMt+LkQbaiudYTI4Hrzr24b0TrtQnMaRrC3Yd20E+yMdESNRa0p8qD tqsd4Fsz9TrUGfi8eOTnpS4/Kzrqa0ci8Or7bOiuPmeE/zmOU0K+AOS5qQO955a3 PvfcXemImjbxX0AfLHpXGUaj+T7ksHYhKg17rQ4ca1mHu2LyFgIRxghD/TTSoxBY 0Zwc7PjLTbtcElY0yoqbqoa6IPe5kPOSynBXwtTtAf/VVgpiyI/Go3lLl3xNGTou GWKT/n8F87D29Hs7HqYZ5WxCic/QswqjBiuRDdEpbXl7EPRZJPAjXBJBAId+PWA+ fmC7Rb9CzWub4SgiOpDsPZeu6DpaNKVmlaKuHgXoMiFR8H1GJEYchwnvZP//Ja4X 2tDnATp4k+ISdhaT3vTBFg1fZNJc6m8fxybuwfkPyVWNtFDhXpIpY9xLE7cycLfB xa6eqOagsQbfRnQ7qw67Hme6xfkwDVwYllWUggh4Ar2s0938yQR/ETOw3E2SI1ke ZH49yWZQxqFqpe4D870e3Ld/yFQfXGfYhbvMMoiPbFTI5U09JIeYI7VFOcwoYCNk 9sXMKnw/TcMdouhS+NSw4n4dW8AawEvZWpdmbf4q5MaDK190CIc= =crRh -----END PGP SIGNATURE-----