How to determine Puppy 'type' from a script?

Under development: PCMCIA, wireless, etc.
Post Reply
Message
Author
amigo
Posts: 2629
Joined: Mon 02 Apr 2007, 06:52

How to determine Puppy 'type' from a script?

#1 Post by amigo »

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.

User avatar
MinHundHettePerro
Posts: 852
Joined: Thu 05 Feb 2009, 22:22
Location: SE

#2 Post by MinHundHettePerro »

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
[color=green]Celeron 2.8 GHz, 1 GB, i82845, many ptns, modes 12, 13
Dual Xeon 3.2 GHz, 1 GB, nvidia quadro nvs 285[/color]
Slackos & 214X, ... and Q6xx
[color=darkred]Nämen, vaf....[/color] [color=green]ln -s /dev/null MHHP[/color]

amigo
Posts: 2629
Joined: Mon 02 Apr 2007, 06:52

#3 Post by amigo »

/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.

big_bass
Posts: 1740
Joined: Mon 13 Aug 2007, 12:21

#4 Post by big_bass »

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.p ... 34c8b25129

*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

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#5 Post by sc0ttman »

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)
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

User avatar
MinHundHettePerro
Posts: 852
Joined: Thu 05 Feb 2009, 22:22
Location: SE

#6 Post by MinHundHettePerro »

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
[color=green]Celeron 2.8 GHz, 1 GB, i82845, many ptns, modes 12, 13
Dual Xeon 3.2 GHz, 1 GB, nvidia quadro nvs 285[/color]
Slackos & 214X, ... and Q6xx
[color=darkred]Nämen, vaf....[/color] [color=green]ln -s /dev/null MHHP[/color]

amigo
Posts: 2629
Joined: Mon 02 Apr 2007, 06:52

#7 Post by amigo »

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.

User avatar
sc0ttman
Posts: 2812
Joined: Wed 16 Sep 2009, 05:44
Location: UK

#8 Post by sc0ttman »

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.
[b][url=https://bit.ly/2KjtxoD]Pkg[/url], [url=https://bit.ly/2U6dzxV]mdsh[/url], [url=https://bit.ly/2G49OE8]Woofy[/url], [url=http://goo.gl/bzBU1]Akita[/url], [url=http://goo.gl/SO5ug]VLC-GTK[/url], [url=https://tiny.cc/c2hnfz]Search[/url][/b]

amigo
Posts: 2629
Joined: Mon 02 Apr 2007, 06:52

#9 Post by amigo »

"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: Select all

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: Select all

"PETMENUDESCR='??'"
"PETOFFICIALDEPS='??'"
"PETREGISTER='??'"

User avatar
pemasu
Posts: 5474
Joined: Wed 08 Jul 2009, 12:26
Location: Finland

#10 Post by pemasu »

Here is more info of the newer database format:
http://bkhome.org/woof/pkg-db-format.htm

User avatar
Sit Heel Speak
Posts: 2595
Joined: Fri 31 Mar 2006, 03:22
Location: downwind

#11 Post by Sit Heel Speak »

More food for thought: here, concerning the "rationalized file names" which have been in force since September 2010.

Post Reply