Author |
Message |
amigo
Joined: 02 Apr 2007 Posts: 2641
|
Posted: Mon 24 Jan 2011, 09:12 Post subject:
How to determine Puppy 'type' from a script? Subject description: Old-school or Woof build? |
|
I'm working on some tweaks to the portion of my src2pkg program which creates pet packages. It can create packages for both old-style puppyies or those using the woof build system. I need to know how to determine (from a running script) if the running version is a woof build or old-style. I used to know how to do this, but seem to have forgotten.
IIRC, it had something to do with the PUP_SPECS file or maybe it was a file in /root/.packages. anyway, woof builds contain a file which was not in earlier versions. Can some sharp someone tell me how to do this. This is so that src2pkg can create the proper *.specs file and package database entries.
|
Back to top
|
|
 |
MinHundHettePerro

Joined: 05 Feb 2009 Posts: 855 Location: SE
|
Posted: Mon 24 Jan 2011, 09:30 Post subject:
|
|
Hello,
older puppies had a three-digit version number in /etc/puppyversion, while woof-built puppies have version info in /etc/DISTRO_SPECS.
Puppy214X has both these files, but that's probably an exception.
hth /
MHHP
_________________ Celeron 2.8 GHz, 1 GB, i82845, many ptns, modes 12, 13
Dual Xeon 3.2 GHz, 1 GB, nvidia quadro nvs 285
Slackos & 214X, ... and Q6xx
Nämen, vaf.... ln -s /dev/null MHHP
|
Back to top
|
|
 |
amigo
Joined: 02 Apr 2007 Posts: 2641
|
Posted: Mon 24 Jan 2011, 09:34 Post subject:
|
|
/etc/DISTRO_SPECS must have been what I was thinking of. Hopefully more clarification or confirmation will come through. It may be that 2.14X has integrated the newer version of PPM, so it should be treated as a newer version. The distinction I'm after is the type of package database which is used.
|
Back to top
|
|
 |
big_bass
Joined: 13 Aug 2007 Posts: 1742
|
Posted: Mon 24 Jan 2011, 12:21 Post subject:
|
|
Hey Gilbert
I havent used or built any woof type packages
( I stopped doing that with puppy 4.12 I can
still help out with the older format though ) but
the tips you need would come from this script petspec you most likely need an update of it
http://208.109.22.214/puppy/viewtopic.php?p=441544&sid=547903e3f5a512123bc5c234c8b25129
*BTW that script wouldnt run for me as is (I am not on the base system it requires)
but the info is what you are looking for
someone should be able to help with the new format
that is currently building with those packages
Joe
|
Back to top
|
|
 |
sc0ttman

Joined: 16 Sep 2009 Posts: 2572 Location: UK
|
Posted: Mon 24 Jan 2011, 15:02 Post subject:
|
|
MinHundHettePerro wrote: | Hello,
older puppies had a three-digit version number in /etc/puppyversion, while woof-built puppies have version info in /etc/DISTRO_SPECS.
Puppy214X has both these files, but that's probably an exception.
hth /
MHHP |
Checking distro specs, pup version from ther sfs (if found) and /etc/puppyversion combined should be enough... but there are always exceptions with their own mix of these settings...
(214X, Puplite, Fluppy etc)
_________________ Akita Linux, VLC-GTK, Pup Search, Pup File Search
|
Back to top
|
|
 |
MinHundHettePerro

Joined: 05 Feb 2009 Posts: 855 Location: SE
|
Posted: Mon 24 Jan 2011, 18:47 Post subject:
|
|
Thinking a bit more:
I suppose the file root/.packages/woof-installed-packages would be unique to woof-built puppies, it's created in the woof-build process.
hth /
MHHP
_________________ Celeron 2.8 GHz, 1 GB, i82845, many ptns, modes 12, 13
Dual Xeon 3.2 GHz, 1 GB, nvidia quadro nvs 285
Slackos & 214X, ... and Q6xx
Nämen, vaf.... ln -s /dev/null MHHP
|
Back to top
|
|
 |
amigo
Joined: 02 Apr 2007 Posts: 2641
|
Posted: Tue 25 Jan 2011, 05:11 Post subject:
|
|
Okay, MinHundHettePerro, that seems to be more or less what I'm after. I'm not really concerned with the version number -I just need to kow that PPM is using the later database style -or not.
|
Back to top
|
|
 |
sc0ttman

Joined: 16 Sep 2009 Posts: 2572 Location: UK
|
Posted: Tue 25 Jan 2011, 16:29 Post subject:
|
|
MinHundHettePerro wrote: | Thinking a bit more:
I suppose the file root/.packages/woof-installed-packages would be unique to woof-built puppies, it's created in the woof-build process.
hth /
MHHP |
This may be irrelevant information for your purposes, but I believe any Puppy that has DISTRO_SPECS, that has been also remastered using the remasterpup2 script (newer versions) willl have the woof-installed-packages file, regardless of its puppy version...
Sorry if this is irrelevant or incorrect.
_________________ Akita Linux, VLC-GTK, Pup Search, Pup File Search
|
Back to top
|
|
 |
amigo
Joined: 02 Apr 2007 Posts: 2641
|
Posted: Tue 25 Jan 2011, 17:08 Post subject:
|
|
"any Puppy that has DISTRO_SPECS" and any puppy that does not have DISTRO_SPECS will be one which does not use the modern PPM database entries like this:
Code: |
ereadfile-0.1|ereadfile|0.1||BuildingBlock|56K||ereadfile-0.1.pet||Read html and txt files||||
|
I'm trying to avoid dealing with *version numbers* -they don't mean anything in puppy anyway. I just need to know the correct databse format. The old ones looked like this:
Code: |
"PETMENUDESCR='??'"
"PETOFFICIALDEPS='??'"
"PETREGISTER='??'"
|
|
Back to top
|
|
 |
pemasu

Joined: 08 Jul 2009 Posts: 5484 Location: Finland
|
Posted: Tue 25 Jan 2011, 17:28 Post subject:
|
|
Here is more info of the newer database format:
http://bkhome.org/woof/pkg-db-format.htm
|
Back to top
|
|
 |
Sit Heel Speak

Joined: 30 Mar 2006 Posts: 2595 Location: downwind
|
Posted: Wed 26 Jan 2011, 03:57 Post subject:
|
|
More food for thought: here, concerning the "rationalized file names" which have been in force since September 2010.
|
Back to top
|
|
 |
|