That's spectacular, and even so it's functionality is gonna get integrated into dir2pet -- where's the backup area that sentry uses?amigo wrote:The --backup function does exactly as you describe -any file about to be overwritten is copied over to the backup area and is then available to be written back. This is a really cool feature and is fully usable with src2pkg using the '-SAFE' option -it guarantees that your system will be the same as before -even before packing is finished.
But will it create the pet.specs entry, the .desktop entry, and the database entry?As far as not making pets directly, I did post a patch here which makes src2pkg do that -except I didn't quite have all the details correct with the md5sums, I think. A small alteration with the 'correct' method as used for tgz2pet should fix it. Barring that, simply creating a normal tgz/tbz/txz package with src2pkg and then running tgz2pet would still be much simpler than running the several commands you are currently using.
Nice.Another thing you might find useful is that src2pkg uses a patched version of tar which works directly with pets -it 'knows' that they are tgz's so you don't have to do all the renaming and re-renaming. Also, the tar version used by src2pkg (very old tar-1.13) is used purposely because of some special behaviours which are not available in later versions -having to do with the way it preserves perms/properties of links, dirs and files. This is why slackware and src2pkg still use it.
But that's why PETs are so FUN! LOL.One of my collaborators has gotten src2pkg creating *.deb packages (which was in my plans all along -as well as rpm's), so I may roll the pet-creation code back in along with the other varieties. As mentioned already, the real 'problem' with building pets is that they break so many of the 'rules' of what constitutes a 'sane' package, so some of src2pkg's best investigations and corrections would have to be overridden to allow for pet creation.
Seriously though, if it creates FULLY compliant pets (including pet.specs and .desktop and database entry) then it'd be great. I still will continue to develop pcompile some, admittedly it's not quite as nice as your tool, but we've put this work into it already and I'd like to at least see it released to a version that does the functions we've already worked out for it.
Chances are I may throw my vote in for using src2pkg as a default builder in future Puppy versions, because it does sound nice. But this /is/ the discussion thread for pcompile.
I really do appreciate the input you've given, and sentry is perhaps the best thing I've seen yet - as it's something I was hoping for - to the point of spending an hour on google - to do. I appreciate that you've created an awesome tool, and believe me, if it can create a good tgz or even an uncompressed directory (as we can just dir2pet once ready, to create our petspecs) it'll probably be what I end up using once 0.2.0 is completed in pcompile (because I don't know enough about coding and all that to go through detecting the other formats, and because it's really just going to remain a simple tool I think for fast builds).
But this isn't the thread for proselytizing ($5 word). Appreciate all the help: yes. Constant advertisements for src2pkg: not so much.
Anyhow, rounding out this post, repeat my earlier question:
Where's sentry's "backup area" located?