The time now is Sun 22 Apr 2018, 01:17
All times are UTC - 4 |
Page 1 of 2 [25 Posts] |
Goto page: 1, 2 Next |
Author |
Message |
tlchost
Joined: 05 Aug 2007 Posts: 2051 Location: Baltimore, Maryland USA
|
Posted: Tue 28 Jul 2009, 20:07 Post subject:
Puppy Online Database Subject description: User Maintained Database for information - pet, sfs and derivatives |
|
There is a new online database for Puppy pet and sfs files, and another one is in development for derivatives.
The database is user maintained, has minimal eye candy, and can be searched on any field.
The goal of the database is to provide a location where information about pets and sfs files can be easily found and accessed.
None of the files are stored on the site, but links to the files and appropriate discussion areas are maintained.
The database structure is as follows:
--------------------------------------------------------------------
ID:
Name:
Date:
ITEM_Name:
ITEM_Type:
Desktop
Utility
Document
Network
Fun
System
File_System
Calculate
Internet
Drivers
Setup
Graphics
Personal
MultiMedia
Windows_Manager
INFO_URL:
DOWNLOAD_URL:
Purpose:
Notes:
Comments:
--------------------------------------------------------------------------------
Sample Entry
------------------------------------------------------------------------------
ID: 1
Name: tlchost
Date: 21-May-2009
ITEM_Name: growler-amp_412.sfs
ITEM_Type: Internet
INFO_URL: http://www.murga-linux.com/puppy/viewtopic.php?t=40483&search_id=50260657&start=21
DOWNLOAD_URL: http://minipc.org/lamp/growler-amp_412.sfs
Purpose: LAMPP(Apache,phpMyAdmin,MySql) for puppy
Notes: For web development, virtual hosts may not work correctly on bootable USB drive.
Comments:
---------------------------------------------------------------------------------
If you know of, or have developed a pet or sfs that you feed should be included in the database, or simply want to view it, please visit
[url]puppylinux.us[/url]
I am in the process of finalizing the structure for a database to handle derivatives. At this point the I'm thinking of
---------------------------------------------------------
ID:
Name:
Date:
ITEM_Name:
PUPPY_BASE:
Kernel:
INFO_URL:
DOWNLOAD_URL:
Purpose:
Notes:
Comments:
--------------------------------------------------------
Comments and suggestions are requested and voluteers who can assist in information checking and/or editing are welcome.
Thom
Last edited by tlchost on Sat 01 Aug 2009, 12:51; edited 1 time in total
|
Back to top
|
|
 |
Lobster
Official Crustacean

Joined: 04 May 2005 Posts: 15238 Location: Paradox Realm
|
Posted: Tue 28 Jul 2009, 23:06 Post subject:
Re: Puppy Online Database Subject description: User Maintained Database for information - pet, sfs and derivatives |
|
tlchost wrote: |
The database is user maintained, has minimal eye candy, and can be searched on any field.
|
Well done
Are you intending to integrate/work with this initiative?
http://www.petstore.puppyspace.org/
tlchost wrote: |
Comments and suggestions are requested and volunteers who can assist in information checking and/or editing are welcome.
Thom |
I hope you and Guy find volunteers
but you may end up having to find, upload and maintain
(there are those that love the idea of helping
and then there are those with the capacity)
Any volunteers?
_________________ YinYana AI Buddhism
|
Back to top
|
|
 |
tlchost
Joined: 05 Aug 2007 Posts: 2051 Location: Baltimore, Maryland USA
|
Posted: Tue 28 Jul 2009, 23:37 Post subject:
Re: Puppy Online Database Subject description: User Maintained Database for information - pet, sfs and derivatives |
|
Lobster wrote: | tlchost wrote: |
The database is user maintained, has minimal eye candy, and can be searched on any field.
|
Well done
Are you intending to integrate/work with this initiative?
http://www.petstore.puppyspace.org/
|
Thanks for the compliment. I don't think the petstore and this project can be integrated....they have different design bases. I suppose each one could reference the other.
Lobster wrote: |
I hope you and Guy find volunteers but you may end up having to find, upload and maintain
(there are those that love the idea of helping and then there are those with the capacity)
|
Good point....but like the various things I've given to others...if they use it wisely they profit...if they don't, then it's their loss.
Hopefully there will be a number of folks that take the small amount of time to make entries so that others will benefit
Sort of like like teaching a man to fish instead of giving him a fish when he's hungry.
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 8526 Location: Perth, Western Australia
|
Posted: Wed 29 Jul 2009, 07:36 Post subject:
|
|
Hi, it's ok to have your own database, but you should get it to generate a database-file in the format now used for Woof-builds, and which will be the standard for future puppies.
http://puppylinux.com/woof/index.html
http://puppylinux.com/woof/ppm.htm
http://puppylinux.com/woof/pkg-db-format.htm
A script on your site could generate that database file, and then the Puppy Package Manager can read it and offer the packages for installation.
Note that all pet packages built by recent alpha puppies using the 'dir2pet' utility have a 'pet.specs' file in them which is the database entry for that package.
_________________ http://bkhome.org/news/
|
Back to top
|
|
 |
tlchost
Joined: 05 Aug 2007 Posts: 2051 Location: Baltimore, Maryland USA
|
Posted: Wed 29 Jul 2009, 09:16 Post subject:
|
|
BarryK wrote: | Hi, it's ok to have your own database, but you should get it to generate a database-file in the format now used for Woof-builds, and which will be the standard for future puppies.
|
It appears that the only way that would work is if the database
structure was changed to be in this format:
http://puppylinux.com/woof/pkg-db-format.htm
Would that mean whoever adds to the database would have to enter all the information in the above format?
I did not envision the database to be as sophisticated as to install things, but simply offer a description and a link to discussion threads and/or downloads.
Perhaps what you're detailing could be a future database project.
Thanks for the input.
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 8526 Location: Perth, Western Australia
|
Posted: Wed 29 Jul 2009, 20:04 Post subject:
|
|
Your suggested database entries, description, puppy-base, etc., already cover what would be in the standard puppy data base format.
It would just be a matter of reading that information, plus the subdirectory where the package is located and name of package, and generating a database file that the PPM can read.
Not hard at all.
The only thing extra is the dependencies. This is something that is overlooked by the various PET repos, but is most important. The user can be asked to enter a list of other pet pkgs that are dependencies, if they aren't already builtin to Puppy -- the format in which that list is entered would be up to you, it could just be a comma-separated list.
-- the only difference in my standard database entries is that each dependency is prefixed with a '+' or a '-' -- again, a script can easily insert that.
In other words, it does not require a "future database project", just a script that can read your database and generate the standard puppy database file. It would be a single file, and all I would need to know is the URL of the file and I can point the PPM to it.
Of course, if you are not into Bash scripting, then you would need help to do it.
_________________ http://bkhome.org/news/
|
Back to top
|
|
 |
tlchost
Joined: 05 Aug 2007 Posts: 2051 Location: Baltimore, Maryland USA
|
Posted: Wed 29 Jul 2009, 21:58 Post subject:
|
|
BarryK wrote: | Your suggested database entries, description, puppy-base, etc., already cover what would be in the standard puppy data base format.
In other words, it does not require a "future database project", just a script that can read your database and generate the standard puppy database file. It would be a single file, and all I would need to know is the URL of the file and I can point the PPM to it.
Of course, if you are not into Bash scripting, then you would need help to do it. |
The database is flatfile....and the application is in perl. I'd be happy to setup the fields to do what you're saving.
The current database entry looks like this
13|gposil|16-Jul-2009|OpenOffice310_JRE_lzma_413.sfs|http://|http://gposil.com/sfs/OpenOffice310_JRE_lzma_413.sfs|OpenOffice 3.10|||gposil
Thom
Most likely I could use some help with the scripting....I have a habit of shooting myself in the foot...and I'm getting low on toes.
I have a trepidation....how can we assure the information input will be accurate? Perhaps I've missed something.
|
Back to top
|
|
 |
gposil

Joined: 06 Apr 2009 Posts: 1305 Location: Stanthorpe (The Granite Belt), QLD, Australia
|
Posted: Wed 29 Jul 2009, 23:13 Post subject:
|
|
tlchost,
as long as we put a PACKAGES.txt file with the database entries as follows:
pkgname|nameonly|version|pkgrelease|category|size|path|fullfilename|dependencies|description|
we will be right
_________________
Dpup Home
|
Back to top
|
|
 |
tlchost
Joined: 05 Aug 2007 Posts: 2051 Location: Baltimore, Maryland USA
|
Posted: Wed 29 Jul 2009, 23:37 Post subject:
|
|
gposil wrote: | tlchost,
as long as we put a PACKAGES.txt file with the database entries as follows:
pkgname|nameonly|version|pkgrelease|category|size|path|fullfilename|dependencies|description|
we will be right |
I can understand what Barry wants/needs .... but I also want stuff that a non-tekkie user, like me, might need.
What I don't see in the above is kernel....and for me, I need to know what kernel is used because my Acer laptop doesn't live with all kernels.
I think if we all work together, things will really convenient for folks....I look at the Online Database as an entry portal, what you have done as detailed information and source for downloads, and what Barry wants to do as "official"
I can see that the pet/sfs database needs to have a 'category' field added....I think I'll use what you have to cut down the confusion...
Now to modify the database without destroying it....I guess I may loose some more toes as I aim for me feet.
Thom
|
Back to top
|
|
 |
russoodle

Joined: 12 Sep 2008 Posts: 716 Location: Down-Under in South Oz
|
Posted: Thu 30 Jul 2009, 06:34 Post subject:
Wanna borrow some more toes? |
|
tlchost wrote: | .... but I also want stuff that a non-tekkie user, like me, might need.
Now to modify the database without destroying it....I guess I may loose some more toes as I aim for me feet.
Thom | I'm another non-tekkie user and what i know about scripting wouldn't fill a flea's ear but i reckon i might have some toes with Puppy's name on, so if you think i could help in some way, give me a holler.
russoodle
_________________ The mud-elephant, wading thru the sea, leaves no tracks..
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 8526 Location: Perth, Western Australia
|
Posted: Thu 30 Jul 2009, 06:41 Post subject:
|
|
The kernel, yes, I was thinking of adding that to my database, as field-14.
There are currently three optional fields on the end,
compiled-distro|distro-release|repo-name|
For example:
ubuntu|jaunty|official|
...means that the package was compiled in Ubuntu Jaunty (or our equivalent Upup) and is hosted on the 'official' repo at ibiblio.org.
Any of those fields are optional, and probably in most cases the 'repo-name' could be left out.
Anyway, I might support this:
ubuntu|jaunty||2.6.29.6|
That is, the kernel it is compiled for as field-14. The line must always have a trailing '|'.
But, I was thinking of supporting a notation like this
+=2.6.29.6
==2.6.29.6
-=2.6.29.6
Using the '+' instead of '>' and '-' instead of '<' as we use gtkdialog which has xml files and need to avoid '>' and '<' characters (I have code that filters them out).
The meaning would be that '+=' the package is designed for that kernel version or greater, '==' the package must be used with that kernel only, '-=' the package must be used with that kernel or less.
No prefix, just '|2.6.29.6|' would be just informational, stating what kernel was used.
I will probably be extending the dependencies field to support package versions, with these '+=', '==' and '-=' prefixes.
No problem if your database has the normal '>=' or '>=' or '>' or '<' as I can translate it.
Note, if a PET package is compiled for the Puppy 4.x series, those extra fields should be at least:
|puppy|4|||
...recommended to have that information, aids the PPM to filter out inappropriate packages.
_________________ http://bkhome.org/news/
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 8526 Location: Perth, Western Australia
|
Posted: Thu 30 Jul 2009, 06:48 Post subject:
|
|
In other words:
pkgname|nameonly|version||category|size|path|fullfilename|dependencies|description|puppy|4||
...extra info on the end to show this package is compiled for Puppy 4.x.
Of course, an architecture-independent package, one that only has scripts, may work on any puppy, Upup, Dpup, Ppup, Tpup, etc., so leave those last fields off or just empty:
pkgname|nameonly|version||category|size|path|fullfilename|dependencies|description||||
_________________ http://bkhome.org/news/
|
Back to top
|
|
 |
BarryK
Puppy Master

Joined: 09 May 2005 Posts: 8526 Location: Perth, Western Australia
|
Posted: Thu 30 Jul 2009, 06:51 Post subject:
|
|
I am also discussing this in my blog:
http://puppylinux.com/blog/?viewDetailed=00931
_________________ http://bkhome.org/news/
|
Back to top
|
|
 |
tlchost
Joined: 05 Aug 2007 Posts: 2051 Location: Baltimore, Maryland USA
|
Posted: Thu 30 Jul 2009, 08:42 Post subject:
Re: Wanna borrow some more toes? |
|
russoodle wrote: | I'm another non-tekkie user and what i know about scripting wouldn't fill a flea's ear but i reckon i might have some toes with Puppy's name on, so if you think i could help in some way, give me a holler. |
I can think of lots of ways that folks missing toes can help. Once I add a drop down selector for catagories, I can see that folks using a pet/sfs file. even if they didn't develop it, could add information.
Have you looked at the database? I'm open to comments and suggestions.
Thanks,
Thom
|
Back to top
|
|
 |
tlchost
Joined: 05 Aug 2007 Posts: 2051 Location: Baltimore, Maryland USA
|
Posted: Thu 30 Jul 2009, 09:09 Post subject:
|
|
BarryK wrote: | In other words:
pkgname|nameonly|version||category|size|path|fullfilename|dependencies|description|puppy|4||
|
The | in a field causes a problem, as the application uses | as
as a marker for the beginning of a field. Is there anyway around that?
[quote="BarryK"]
...extra info on the end to show this package is compiled for Puppy 4.x.
.............
so leave those last fields off or just empty:
If no information is entered for a field, there is nothing before the | end of field marker.
So, a name database for First, Middle, Last might look like this
|Sam||Smith
|Alfred|E|Newman
If you think it might be of help, I can set up a database that we can use for testing.
Thanks for considering adding kernel information....and I'll watch the blog.
Thom
|
Back to top
|
|
 |
|
Page 1 of 2 [25 Posts] |
Goto page: 1, 2 Next |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You can download files in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|