So, I created a script that tracks all dependencies of fluidsynth~.pd_linux and copies them to the local folder.
On Sun, 2021-01-10 at 17:14 +0100, Roman Haefeli wrote: > > What I'm still wondering is how to distinguish dependencies required > to > be included into a Deken package from those that we assume are > already > installed on the system. Is there a proper way for making that > distinction? Without that distintion, I'll probably have to hard-code > all those libs that shouldn't be included in the final package. This is the approach I used. I checked all libraries from ldd output which package they belong to with `apt-file search` and checked what happens when I emulate to uninstall that package with `apt-get remove --dry-run <packagename>` If the system would get horribly broken, I assumed the package is essential to the system and thus it is likely to be installed on any system. I made a hard-coded list of regex patterns matching those library names. Libraries matching any patterns of the list are not included in the final package. Does that approach make sense? See PR: https://github.com/porres/pd-fluidsynth/pull/5 Roman
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Pd-dev mailing list [email protected] https://lists.puredata.info/listinfo/pd-dev
