So it would be a good idea that double clicking a package would install it offering to install the dependencies as well.
Good idea.. Gpkgdialog (the GUI for Pkg) can (kinda) do it already
, my Akita puplet had that feature - click on a PET in ROX, and if
that PET was found in a repo, then the deps could be auto downloaded/installed too
My current implementation is too slow and annoying - it searches deps as soon as you click on the PET..
A better way is to popup the GUI with a 'Get Dependencies' button ..
I will make sure to fix it up and make it work properly (if I can)...
Do you know that mistfire supports a wide range of packages in his X-Slacko Slim?
Thanks, I will have a look .. I didn't.. See what I can 'borrow'
*Currently* Pkg can work with packages from:
Puppy (.pet), Slackware (.tar.*, txz, tcz, tgz), Debian and Ubuntu (.deb), Arch (.pkg.tar.*), CentOS (.rpm), ...others??
... I used pkg to install mednfen from the Arch repo, worked fine.. Although I didn't test it fully..
It's a bit awkward that you cannot see in ppm when/what you've "installed" by sfs. You also do not know whether some dependencies
for your installed pets are met by a sfs; you better not uninstall the sfs then.
I have had the same thoughts ... It's awkward to have SFSs installed and the pkg manager knows nowt about them..
Pkg *could* be made to register SFS as installed packages, just like PET files.. Note made.. I will look into it, thanks.
It may break more than it solves though, will have to check it out!
Thanks for the ideas, will look at X-Slacko soon ..
wiak wrote:Unfortunately, I've been so busy coding makepup I've not had time to check your package manager out yet.
I wouldn't bother testing the version I attached earlier, lots and lots has changed, feedback from it will be irrelevant now...
I'll certainly be giving it a spin once I finally take a rest from makepup (only a few tiny extras I want to add to that for the moment -
sometimes it is good to sit back and ponder for a bit before deciding on more...)
wiak
Makepup looks nice... I haven't even rebooted my puppy for like 4 days, so I'm not about to make a new puppy build, so can't test it yet..
My thoughts making a woof wrapper (which I might do straight after Pkg):
Should be a dialog based menu, like buildroot...
* choose base distro (gives the repos you will work with)
* choose kernel (the list u get depends on base distro choice..?)
* choose boot loader (syslinux, grub)
* choose defaults boot options, lang, keyboard, etc
* choose PET selection (if i can make Pkg and chroot play nice, Pkgdialog can seamlessly step in in here
)
* choose desktop environment (apply various SFS [or PET collections])
* choose themes, wallpapers, etc (add the files, sed the configs)
Something like this (but simpler):
^ Notice the SAVE and LOAD buttons ... This lets you save and load your custom build config so that you (or others) can re-build one
of any previous builds that have been successful ...
Woof (makepup?) could save all the custom files, pkgs, configs, repo files, etc to a
./build/slacko_xfce4-6.9.9.9-k4.2.5.6/
./build/slacko_xfce4-6.9.9.9-k.4.41.6.22/
etc
..but probably such a "Woof-menu" would need to be a frontend to a CLI wrapper of the woof scripts.. not just a wrapper to woof itself..
Any chance of making a makepup menu based on dialog?