-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Tue, 26 Mar 2019, Andrew Gregory wrote:
On 03/26/19 at 02:52pm, Erich Eckner wrote:
Hi,
I'm looking into creating links databases for archlinux32 and saw (thanks, Eli) that they are created asynchronously by systemd timers here: https://git.archlinux.org/infrastructure.git/tree/roles/sogrep/files
I was wondering, if it wouldn't be better to create them during repo-add (and repo-remove) at a similar point, where *.files.db entries are created - ignoring deltas (can we ignore deltas already?), this would be somewhere down in db_write_entry() in repo-add - but even including deltas, it should not need changes at too many places.
However, before I start trying to patch repo-add and repo-remove to maintain a *.links.db, I wanted to ask if there are any objections to include this functionality there.
What is a links database?
Hi, sry, I should have been clear - I mean this one: 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. regards, Erich -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAlyal5MACgkQCu7JB1Xa e1p9Nw/+OTkQCO+3HmnQnoy7lEMqsWvKTejrzNc1XogX050OhRufbdc4vF1cPyKR l98paeIHwp9q/sUoRKLmdrWetboJB5bEpJqCZqNx2Ik05FQPQzUzj/NFFXuBnYeK +uppeM8EU0NDPxTCjvwZP4GJklrkl1GcWthIz1HS/nVhZROQ/1iXEH7Vnmr3LY9f bHLXiQv8AlF37SvkjRM0DtnBQVPsbb8rPWz2nIWkykgGFiMH73j8tR0h0+/Hti9m euY3BhtZiBl2LQdW+XZ4LMFjgSTVXE338cYayP95KZ7Lo/QuuePSLiLOW8a4ao8y 7YF2Oa8eOdA/GaIvT4zWDMR+jW7mud2b9HovTmNRGE+ZAqdr5S+FTn2J993/oLab huzzqPzQALzYvruwse3sfHaTY2rRpr7OEVAkWR2rGYYOVACygAxSoFpHVRTerWGG 4kOKvnGcJJ9HLfQwHmJ7KMx/sa6KAjitDeWZFMnmjoZyqL5H7xucPcaSy7zpo9df WoEtJXfEDRDi/Amvfa6ub6HbYsOLOggGraDuwSj28G1L6jgbpwm/wYdwEdqDbngZ T3et2BeHET/n5mgtpvlTkbFEdVK0CasR4He15bd0JuBPF5HPXVKx/MglTbC+oD6n OJejPzusOHd1L/u5ZSsESKmyuUsN14tMn1chgO32LrkQfJmW/yg= =6u7q -----END PGP SIGNATURE-----