builtin_files problem

[rizalmart]

I noticed that on the entries of DISTRO_PKGS_SPECS like this for example

yes|xserver_xorg|xorg-server,package-a,package-b|exe,dev

When the packages become a builtin, Its database entries are successfully entered on the /var/packages/woof-installed-packages file. However the list of files installed by the packages merged as one package entry based from the entry in DISTRO_PKGS_SPECS

for example if a sample DISTRO_PKGS_SPECS entry shown above was installed. The builtin-files was /var/packages/builtin_files/xserver_xorg

Instead of /var/packages/builtin_files/xorg-server /var/packages/builtin_files/package-a /var/packages/builtin_files/package-b

Which is the correct one.

Is there anyway to fix this problem on builtin_files.sh of woof? If the problem was fixed it was much easier to audit files and repack a packages.

[sc0ttj]

I think I have encountered this issue when using Pkg too - trying to find which package a file comes from is made tricker in these cases, if the package in question is a built-in..

I would generally argue that the package names listed in ./built-ins/, and the listed file contents of each package, should reflect the repo packages as accurately as possible.

[sc0ttj]

Puppy version: FossaPup64 9.5

I was trying to find out which package the /usr/sbin/puppyapps script comes from:

• it is not listed as an installed package (built-in)

I tracked it down, by knowing that the 'noarch' repo "is a thing"... Other users (beginners) might not know about it..

https://github.com/puppylinux-woof-CE/woof-CE/blob/de4d4c679f0cd079e38e56b0fddd0da76f752015/woof-distro/Packages-puppy-noarch-official

Other packages which originate from the 'noarch' repo, such as PupClockSet are listed.

...I would argue that pkg which /path/to/some-script-from-builtins should always be able to return a package that exists in one of the installed repos.

[rizalmart]

@dimkr

Hello can you please fix this issue on woof-ce upon processing builtin packages?