(old)Puppy Linux Discussion Forum

This is in Woof, but all Puppy developers using 4.3.1 or later can use these scripts. That is, anyone who uses dir2pet to create a PET package.

I have made small improvements to make more appropriate selections of some of the fields in the package database entry.

Two scripts are affected, dir2pet and petspecs, that reside at /usr/bin.

A couple of bugs fixed. These scripts are in Woof, March 4, 2010, and they live in /usr/bin. Attached...

BarryK wrote:This is in Woof, but all Puppy developers using 4.3.1 or later can use these scripts. That is, anyone who uses dir2pet to create a PET package.

I have made small improvements to make more appropriate selections of some of the fields in the package database entry.

Two scripts are affected, dir2pet and petspecs, that reside at /usr/bin.

Hi Barry it would be nice if you added a strip bins and .so files to script, so when you run new2dir it would automatically strip the bin,so files
ttuuxxx

I have a patch for dir2pet (dir2pxt via symlink) that will allow either xz or gz compression (xz is about 10-30% better and just as fast to decompress) I have also previously patched petget as well, and added tar.xz support while I was at it (for new arch and slack packages) If you are interested, I need to resync with woof anyways if it would be better to get the patch using bones.

I had also made a fully gui version as part of Pcompile that combined the two, but it was missing a couple of features that are in dir2pet and I plan to eventually rewrite it using amigo's src2pkg. It actually stripped bin and .so including removing gcc notes and comments (the gui was called adoptpet, but was basically broken out into the gui adoptdir which was incorporated in adoptpet and adoptpxt)

Why not try using src2pkg itself? It already has loads of features just up Puppy's alley, including strip, compress, culling of files, supports both old and new *.specs files. Plus, it knows how to build all sorts of sources -mostly with out any help. It uses a forked version of installwatch which tracks many more system calls and more reliably. src2pkg scripts provide a perfect concise, yet extendable API for scripting the creation of any package. Already built-in support for extensions for anything you find missing or for proposed additions to main code. 5 years and going strong...
http://distro.ibiblio.org/pub/linux/dis ... d/src2pkg/

src2pkg pet here:
http://distro.ibiblio.org/pub/linux/dis ... arch-7.pet

I like it just as it is - and it will probably be in the devx of 4.4. I just want to setup a basic gui frontend to it (probably after 4.4), unless you have already added one yourself.

technosaurus wrote:I have a patch for dir2pet (dir2pxt via symlink) that will allow either xz or gz compression (xz is about 10-30% better and just as fast to decompress)

I mentioned that about 6+months ago on Barry's blog and even gave actual examples but never received a response
ttuuxxx

How do I use new2dir? I have been trying but it just makes an empty directory. If I just run

toomuchcomputertime wrote:How do I use new2dir? I have been trying

Code: Select all

new2dir make install

but it just makes an empty directory. If I just run

Code: Select all

 make install] the programs install, so I know they work. 

Thanks, I hope I am not hijacking your thread.:oops:

first you need to install the compiler/devx, then usually you configure it.
Barry likes ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --build=i486-pc-linux-gnu
then you type make
then you type new2dir make install
ttuuxxx

GUI error:


http://murga-linux.com/puppy/viewtopic.php?t=58615

Likely I'm speaking out of turn here but for a new user ( tahr 6.0 and lxtahr 15.02) making a petwith Dir2Pet is still a might tricky.
example:
quote from pet.specs:
"Opencpndepends-0.3|Opencpndepends|0.3||BuildingBlock|7168K||Opencpndepends-0.3.pet|trusty|no description provided||trusty||"

if I create THIS pet,and try to install it, I will more than likely get an error message something like this:
"...pet is named..Will not install!"
The folder Opencpndepends-0.3 is not named as a pet.
It took me awhile to figure out what ( I think )the issue is....it is that the petspecs file contains ".pet".

But It wasn't me that added that ".pet" in the FullPackage Name.oh, sure- It seemed to make sense and one tends to accept what an official app does so I left it alone-.

But If I get rid of the ".pet", here,in the dialogue, it works fine. and I can stop chasing my tail .rowr.

here's another example...a downloaded pet to be installed to Tahr6

Again, as in above post, if I extract it and rebuild it, (still on the fat hdd) it installs fine- Perhaps it has something to do with installing saved pet files from Fat32 hdd while puppy is kenneled on a usb stick? or is it Rox? because it doesn't happen in LXTahr....Puppies do pee in weird places...

hi,

is there a way to specify a command to run immediately after install?

thx!

A more experienced person could probably answer better, but I'll direct you to this thread where I recently learned about the pinstall.sh script (there's an example in that thread too, in my driver .pet): http://www.murga-linux.com/puppy/viewtopic.php?p=843020#843020

It's added in the top level directory before running dir2pet. The script is then executed automatically when the .pet is installed.

cimarron wrote:the pinstall.sh script... It's added in the top level directory before running dir2pet. The script is then executed automatically when the .pet is installed.

thx, that worked!