Hello,
As a long time Puppy user, and small time Developer, I find myself typing the same code again and again... Being a half blind arthritic Dyslexic, well, I hate to type..
I have found that many things are easy enough to Open up in Puppy, but some are not so easy to pack back up again..
Examples:
To open an ISO in Puppy, you click on it..
But for newer users, repacking it into a bootable ISO isnt as "one click" easy..
The same applies to an SFS file..
Or how about unpacking, editing, and repacking the initrd??
Or tarring/untarring directories...
And of course, compiling a source tarball into a pet...

So I have written a simple GUI to aid in these processes..

The first button opens a window for you to put the contents of your ISO into.. Clicking OK turns it into a bootable ISO..

The second does the same for SFS files...

The third allows you to link an initrd into it, unpacks it for editing, and when OK is clicked, repacks it into an initrd again...

The fourth will unpack and/or repack tarballs...

The fifth button in a front end to Amigo`s awesome src2pkg..
Drop a source tarball into the window, click OK, and (hopefully) get a pet..
src2pkg must be installed separately, I will post a pet...

A lot more to do, this is just an alpha...
Testing needed.. any takers???

Src2pkg is available, as a pet, @ my meownplanet link in my signature, or on the Forum, or from Ibiblio.org...

Hello,
@Amigo,
Thank you.. The link to my dir is currently down..
DevTools uses a script to launch src2pkg, using the -PET2 option, launching it in a terminal, for feedback as it works..
I still have to learn about the options..
Any Puppy specific options I need to add by default??
BTW, nice program, it is really amazing..

I thought about including Joe`s (Bigbass) GUI for configuration..

Also, the helper didnt build libsentry.so properly, so I built and included it in my .pet..

Hello,
I suppose I should mention...
As an alpha, it has its limitations..
You must be using Rox.. Support for Thunar etc will come later..
You need a lot of room..
Although Tarballs (tar.gz/tar.bz2/tgz) and the initrd can (and should) be hardlinked in, ISO`s and SFS`s can be big, and currently, require you to Hardlink the contents themselves into the directory. Future releases will mount and link automatically, but this is an alpha... I have not setup the "mount/unmount" and first run stuff yet... I have limited "Puppy Time" atm....

I really made this for my own usage, via CLI scripts, (of which there are several in line for future inclusion), but realized that a GUI might attract newer users into "getting a little `Puppy guts` on their hands"..
Plus, as I stated, I hate to type..

Its pretty basic ATM, the dialog "eye candy" can wait..
Is it functional and user friendly..??
What would you like it to do??

Do you mean that src2pkg-helpers fails to build if you manually run 'src2pkg --setup'? If not, theres a problem in there.

There are lots of interesting options for puppy which are not specific to the pet format. See the advanced options by running 'src2pkg -hh'. You can have src2pkg trim the documents to a bare minimum for you, strip harder, have bins compressed using upx/ucl -many other esoteric stuff there. Have a read through /etc/src2pkg/src2pkg.conf and /usr/libexec/src2pkg/DEFINES for more insight into mayn options. Don't make changes directly in the DEFINES file, instead put any overrides in the conf file.

Note also, that src2pkg can be used to convert packages from one package type to another -with the added bonus of all the complex sanity-checks done by src2pkg

Two options you will find useful for pets/puppy:
LFS_POLICY -look for the line:
#[[ $FHS_POLICY ]] || FHS_POLICY=SLACK
in the /etc/src2pkg/src2pkg.conf file, and change to:
[[ $FHS_POLICY ]] || FHS_POLICY=NONE

src2pkg will complain bitterly(and rightly so!) if you try to build packages which contain your $HOME directory. For puppy this means '/root' and many packages quite wrongly install stuff there. No other package format in the world allows such intrusion into your HOME dir, but puppy keeps lots of stuff there -rant, rant, rant. YOu can't stop src2pkg from complaining about it, but you can make it not choke and refuse to build the package by putting this in the conf file:
FAIL_ON_BAD_DIRS=NO

Of course, all these options can also be passed on the command-line as environment variables:
FAIL_ON_BAD_DIRS=NO FHS_POLICY=NONE src2pkg ..options..
if you don't want to make changes directly in the conf file.

Hello,
@tatamata,
Src2pkg, as Amigo stated above, has the ability to convert package formats, and I intend to create a "Convert" tab to take advantage of that functionality.
After I do a lot more reading. _________________Close the Windows, and open your eyes, to a whole new world
http://puppylinuxstuff.meownplanet.net/puppyluvr/
Puppy Linux Users Group on Facebook
Puppy since 2.15CE...

Conversion from/to should work for any combination of these packages types -except that src2pkg doesn't recognize .taz packages -it only creates them. It could easily support reading them and converting them -I just didn't think about it.

Besides, src2pkg's whole purpose is to foment the repeatable creation of standards-compliant packages. No one can create a program which perfectly does so without limits -it takes a human brain to properly undertsand and act on what the README file in some sources says. But src2pkg at least leverages previous human experience with the sources when possible. So, instead of going haywire in a frenzy of package conversion -try learning to use src2pkg to create new packages from scratch and you'll always be able to repeat your work and pass it around by simply supplying your packages' src2pkg 'recipe' and whatever additional materials are needed.

amigo
Users should note that they will probably need to edit the configuration file to tell src2pkg to create pets instead of some other supported package format.

Hey puppyluvr

Quote:

puppyluvr
After I do a lot more reading

reading about all the options before I made a GUI for the config
took me some time if I remember correctly it was 8 pages
and still I had to ask Gilbert some questions after I read though it all
to set it up correctly for puppy mainly because we are so non standard
to any other linux package but with all those background details aside

you could include my GUI config as an " advanced tool option" if you want to

but you could get the same result forcing those options with the file I will include (below)
and setup the conf file automatically preset with what you will need
by using this file that was generated from my GUI config file tool

Thanks for posting your conf file Joe. I think that for the next version of src2pkg, I will include pre-configured conf files for each system/package type which will give users a faster start using src2pkg.

About your config settings, some of them are not really needed as they reflect the default settings anyway. Still, it is useful to show a range of *possible* settings which users are most likely to want or need to change. And, it should be remembered that many of the possible settings can be over-ridden from the command-line, but only if you use conditional syntax in the conf file, like this:
[[ $PKG_FORMAT ]] || PKG_FORMAT=pet;PET2=1
This syntax also allows each build to have its' own settings, if needed, by setting them in the build script -although this is rarely useful. The above syntax can be read like this:
If the package format has not already been set, then set it to 'pet', etc.
But, any src2pkg CLI options, options set in the build recipe, or personal conf files are all seen *before* the /etc/src2pkg/src2pkg.conf conf file is read -but they will not be respected if the main conf file overrides them with the 'definitive' syntax you show. That's why the more complex conditional syntax is useful -it allows you to keep all options open to change from the CLI. That said, the main conf file has the last word, so using definitive syntax in it allows the system administrator to set any options definitely, if needed.

I hope it is okay to point out that not all of us noobs are good at .tar.gz just like that.
I don't dare to try tar.gz even after three years of daily usage of a linux Os.

What is expected of me to know to get the tar.gz thing right?
How much bigger would it be to upload and download unpacked?_________________I use Google Search on Puppy Forum
not an ideal solution though

[[ $PKG_FORMAT ]] || PKG_FORMAT=pet;PET2=1
This syntax also allows each build to have its' own settings, if needed, by setting them in the build script -although this is rarely useful.

does this work better ?
if so I can do a dialog version of it to generate that output from a GUI as an advanced setup with more possible options even if you include the new conf pre packaged
a front end would still be nice as an advanced option

and a source frontend to gather all the sources like spobkg does
that is already doable and done

I think the name of the utility basically say it in the first word of "Developer".
The utility is not meant to be for the user that has no knowledge of the structure of an iso, SFS, tar.gz, etc.
For what the utility is, for a developer, it is handy. But the average user would need a course on linux in order to make use of it.
Adding a complete hand holding guide for the non- developer just is not an option.

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