How ppm finds missing libs&Potential Arch32Pup Improvements
Posted: Mon 02 Mar 2020, 06:35
For better dependency resolution on Arch32Pup, I'm considering using the %PROVIDES% field that is provided by the arch linux repos in order to find the packages which contain the missing libs. From there, there are three options. These options are:
1. only install the missing libs on their system (i.e. pupngo style),
2. install the whole package or,
3. don't install the missing runtimes and load them as SFSs when needed.
These packages that have the %PROVIDES% filed in their metadata likely have lib in their package name and are likely the runtime for a given package which is listed as a "%MAKEDEPENDS% package for one of the packages installed by the ppm.
Puppy actually already does some of the work here because the puppy ppm, identifies which libs are missing after it finishes installing a package. The first thing I would like to do is trace some of this process. This will give me an idea of how we might incorporate this suggested feature into the ppm.
1. only install the missing libs on their system (i.e. pupngo style),
2. install the whole package or,
3. don't install the missing runtimes and load them as SFSs when needed.
These packages that have the %PROVIDES% filed in their metadata likely have lib in their package name and are likely the runtime for a given package which is listed as a "%MAKEDEPENDS% package for one of the packages installed by the ppm.
Puppy actually already does some of the work here because the puppy ppm, identifies which libs are missing after it finishes installing a package. The first thing I would like to do is trace some of this process. This will give me an idea of how we might incorporate this suggested feature into the ppm.