About libs and other stuffs manually added to a Pupplet iso?

[Argolance]

Bonjour,
This is a problem to integrate manually libs into an iso without them being duly referenced in my pupplet database (/root/.packages/builtin_files) because when installing programs, PPM reports them as missing though it is not the case: is there any trick to solve this?

Thanks.

Cordialement.

[Argolance]

Nobody knows? Is it the right place to ask this question?

Cordialement.

[jamesbond]

I am surprised nobody answered. I have left Puppy PPM for a while now, so please take my answer with a grain of salt.

When you make a PET, you can specify the "dependencies" that the PET needs. These dependencies are recorded in a special field in the pet.specs file. When you install a package, the PPM will check this field to check if all of the dependencies are met (ie, if all the packages specified by these dependencies are installed).

With this model, the only way you can "fix" the problem is either:
a) when you install your libs, update the PPM registry (/root/.packages/PUPPY_OFFICIAL or something - I can't recall) by inserting "fake" package entries that represents the libs that you've installed, or
b) for each libs you want to add, create a PET with the correct package name that represent the libs.

Both are tough if you want to make a "generic" stuff that works for all puppies because the same library may have a different package name for Slackware-based puppies or Ubuntu ones.

[mavrothal]

This is a problem to integrate manually libs into an iso without them being duly referenced in my pupplet database (/root/.packages/builtin_files) because when installing programs, PPM reports them as missing though it is not the case: is there any trick to solve this?

You shouldn't integrate manually libs into an iso...
But since you do, PPM looks at /root/.packages/{devx-only,user,layers,woof}-installed-packages to find what is installed, so add the pkg.specs line from your library package to woof-installed-packages.
If you do not install through a package then you have to make a relevant line and add it there.
Regarding the /root/.packages/builtin_files/package_name file this is there to help "remove" the builtin files. If you also want this you should add the corresponding /root/.packages/package_name.files in /root/.packages/builtin_files using only the main package name (no version etc). If you install without a package, you must also generate this file if you want the package to be "removable".
Alternatively you can use woof...

[Argolance]

Bonjour,
Thank you guys!

You shouldn't integrate manually libs into an iso...

I guess it is not the best to do but:

• - Very often we find here and there/install pets and sfs, containing the main program and libs matching with. As some programs need the same libs, I thought it was better to integrate these common libs directly inside the iso. So, pets and sfs are not "redundant" and much lighter.
  - Sometimes, we install a program that needs libs coming with another program installed too, and if this one is uninstalled, that one doesn't work any more...

Don't know if what I try to explain is clear?
(One must choose the lesser of two evils)

Cordialement.