'petspec' improved

/usr/bin/petspec is a little GUI application that can be run directly but is also called from 'dir2pet' -- the latter is our utility for converting a directory into a PET package.

I have put question-mark buttons alongside some of the fields in the GUI, to explain each field.

In particular, the dependencies box has help, which explains how to enter the dependencies of the package, in particular how to include versioning as introduced here:
http://bkhome.org/archive/blog2/201107/basic-versioning-support-in-woof.html
http://bkhome.org/archive/blog2/201107/progress-on-versioning-support-for-dependencies.html

---

Comments

how to get pet.spec _only_
Username: technosaurus
IIRC you previously asked how to get pet.specs for each package from the repository it just hit me how to improve the speed of this process just do the tarball creation in 2 steps in dir2pet and other pet creators like this: [code]tar -cf $PKG.tar $PKG/pet.specs tar -uf $PKG.tar $PKG[/code] ... add checksum, compression, rename ... then to get the petspecs without having to waste your monthly limit [code]echo downloading $REPO_DIR/$PKG$EXT wget -q -O - $REPO_DIR/$PKG$EXT |gunzip |tar -x $PKG/pet.specs 2>/dev/null & PIDOFTAR=$! while ([ ! -e ./$PKG/pet.specs ]) do sleep .1 done kill $PIDOFTAR echo done[/code] if older packages remain in the repo, the code will still work, but wget will reach 100% b/c pet.specs somehow ends up being the last file added to the tarball

./dir vs. dir
Username: technosaurus
"btw previous code may need an additional ./$PKG/pet.specs after $PKG/pet.specs I almost forgot that the pets/tarballs could have that minor difference (some are top directories in the tarball are ./pkg_name/... while others are just pkg_name/...) perhaps once dir has been verified the ./ could be removed for uniformity cd $DIR/../ DIR=${DIR##*/}

Tags: woof