Build script that make two main sfs, has also defined 'false packages list'

sh-4.2.039-1 libjpeg-8.0.2-1 libsystemd-196-2 systemd-tools-196-2

That is needed because many packages depend on for example libjpeg, but that
package does not exist, instead it is provided by package libjpeg-turbo. Same is with
sh that is provided with bash... and you have now discovered more of that packages:
libusb is provided by libusbx; procps with procps-ng, and util-linux-ng with util-linux.
For libcups problem is different - in original Arch they split cups in two packages, but
when I replaced original cups and libcups with my package forgot to add libcups to
pacman's base. I will add those new packages to false pkgs list for future releases,
probably more of them exist, but no way to easy find them.

no problem sim, because systemd 'used to' also do it, but with the newer release, it all of a sudden stopped. I'm knowing that there may be others....so as i encounter them, i'll report them...so it can be remedied.

when installing a package using yaourt it wants to install linux-headers, even if linux-3.6.8-12.12.sfs is already loaded. the linux-3.6.8-12.12.sfs file should have the folder /var/lib/pacman/local/linux-headers-3.6.8-1 inside of it, so that doesn't happen.

and if the /etc/ssl/certs are inside of the archdev.sfs....it would be nice to have yaourt in the archdev.sfs as well.

also the archdev.sfs has /usr/include/geany inside of it. so if i have the archdev.sfs loaded, and try to install geany, it won't install, saying that those files already exists. is it necessary to have /usr/include/geany inside the archdev.sfs?

these things are minor, but the goal is 'perfect' right? just running into some things that doesn't have to be a minor issue. they can be a 'zero' issue...because they can be fixed.

when installing a package using yaourt it wants to install linux-headers, even if linux-3.6.8-12.12.sfs is already loaded. the linux-3.6.8-12.12.sfs file should have the folder /var/lib/pacman/local/linux-headers-3.6.8-1 inside of it, so that doesn't happen.

and if the /etc/ssl/certs are inside of the archdev.sfs....it would be nice to have yaourt in the archdev.sfs as well.

also the archdev.sfs has /usr/include/geany inside of it. so if i have the archdev.sfs loaded, and try to install geany, it won't install, saying that those files already exists. is it necessary to have /usr/include/geany inside the archdev.sfs?

OK, linux-headers folder will be added for next kernel source sfs.

I added yaourt in only one version earlier because pacmanxg required it, now archdev.sfs has
packer and pistall.sh script inside runs update-ca-certificates, so it works without user intervention.
One package to browser AUR is enough and it will be packer, yaourt is slower and asks
too many questions...

Development files from adrv are also in archdev.sfs, now when I think about it, it's obviously
wrong so i might just move geany to archapps - I have it loaded all the time anyway.

simargl's repos are here: https://bitbucket.org/simargl/
From what I can see (but not tried/tested),
The spkg repo contains the spkg and paka scripts that actually are the building engines for the Archpup packages.
You just clone the repo and run the install script to install them.
The sources repo has just that. Archpup-specific tarballs that are downloaded and installed by spkg
The def-scripts repo contains packman like instructions that tell spkg where to find how to handle the different packages that will be installed.
The archpup repo is where everything happens.
The "arch-tools" folder is like a rootfs-skeleton and contains some puppy-/archpup-specific scripts
The "list" folder caontains the arch-* and spkg-* lists of packages that determine which package to put in which sfs (base, dev, apps and adrv)
Finally the scripts folder contains the 2 scripts that actually build Archpup. mkroot I guess goes first to setup the environment and base follows to do the building.

I hope this helps.
Hopefully simargl or someone that actually tries it, will fill the (inevitably) missing important details and (probably) steps.
(one step that I do not see for example is where the initrd and the ISO are build. unless they are done "manually")_________________== Here is how to solve yourLinux problems fast ==

you know something else that just dawned on me is that i don't think ppl really know that pacman is a 'complete' and easy to use package manager. Just reading the thread title it may be viewed by many as just another puplet by the name of ArchPup. based on Lucid, or Precise or something.

As silly as it may sound, it may register in a lot of users heads as "ArchPup:Made with latest Arch packages.........based on Precise".

Many people may be skipping over it because some of the other titles have a more attention getting headline, and they also don't know pacman's capabilities.

they don't know how easy it is to install those hellishly hard in traditional puppy, favorite apps of theirs using ArchPup, and is just using alternatives apps in a more attention getting 'title' derivative.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum