I made up these scripts for quickly testing new packages - they still need some optimization & cleanup but are working well so far

src2all will convert most src packages to pet and sfs compiled with puppy build environment (t2-486-linux-gnu) with prefix=/usr will post install files from a specified dir and take config options from a specified file

usage:
pcompile - lets you select a source package and add configure options in a gui to be compiled with src2all

They are just bash scripts so they should work with almost any version of Puppy with the corresponding devx (4.1.2 uses devx_412.sfs ... 4.2 uses devx_420.sfs)... note that you will still need to have any of the dependencies installed to compile a package... but if you can't find it - this should make it easier to build the dependencies as well

Right now I only have it set up to configure with a default puppy config, whereas v0.02 should allow advanced configure options to be passed (via a file called <pkgname>.cfg)_________________Check out my github repositories. I may eventually get around to updating my blogspot.

TODO add a dialog for adding files from a directory to the packages (for adding desktop files, icons, addon packages, dependencies and other miscellaneous files)_________________Check out my github repositories. I may eventually get around to updating my blogspot.

Will the splitting off part work for pre-compiled binaries? IE: I would like to grab a slackware .tgz, open it up to its own directory, then have a script that will take that directory and split it into the DEV, DOC, NLS and main... Is this capable of that, or can it be made to do so somehow?

not at the moment but that's not a bad idea - probably a different program though... the applicable bash script to modify would be new2dir or my modification of it 2petnsfs_________________Check out my github repositories. I may eventually get around to updating my blogspot.

Yes, I agree, it would most likely be an entirely new issue... It would however be a WONDERFUL thing for many people I think (not least of all, myself).. As I stated in my PM to you, as per my understanding you are "the man" when it comes to bash.. so if anyone CAN do it... well here I am asking...

well - after using woof & looking through the scripts there - I find out that Barry has already done all the hard work for those package formats (debian, ubuntu, arch, slackware, T2... ) I really need to pull that code and adapt amigo's src2pkg script with the bigbass mods to really puppify it_________________Check out my github repositories. I may eventually get around to updating my blogspot.

it makes the 2.X-4.X traditional (non-woof) style .pet ... other than that I can't think of any reason why it shouldn't work. I plan to look at updating it for 5.X_________________Check out my github repositories. I may eventually get around to updating my blogspot.

I got the pipe and fomit frame pointer args from the Wiki, page at:
http://www.puppylinux.org/wiki/compiling
It also suggested -O2 but somehow the src2all gave a configure error on that argument, so maybe that configure doesn't support -O2...
I got the --prefix=/usr and other default dirs from your "default" line in Pconfig.

As a result, configure does not configure, I go through script, complete pet, get 490 byte pet file with nothing.

Question then: Does the "default string" get auto-prepended to what I put in? If not, what have I done wrong? BTW, must include the disables, as those packages are not part of the build I want and are excess bloat.

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