PETfind

[106498]

Hey all. If you take the time to make and test a package for puppy, wouldn't it be nice if people had an easy way to find it?

I've made a page on the wiki called PETfind, with links to a new page for each category (internet, games, multimedia etc.) The idea is, if you make a package, please add a page to the PETfind index on the wiki. This way we'll soon have an easy way to find all the great software for puppy out there.

Anyone can get an account on the wiki, so there's no excuses!

http://puppylinux.org/wikka/PETfind

I know that there's a category system on the wiki, but you can't seriously expect people to go to the categorysoftware page and click on every program until they find that program that does what they need it to do.

I think this will work. If you think not or have feedback. Please post here. Otherwise, start adding pages for those programs you've made!

Additionally, it would be good to have a somewhat standardised format.

Include: Intro/info, screenshot(optional), link to official site, link to forum thread, links to download locations. State dependancies needed if known.

[pri]

good idea.......

[106498]

People!! Why did no-one tell me there's already something like this at http://puppylover.netsons.org/dokupuppy!

Personally I prefer the format I was using on the puppylinux.org wikka. Some more info on each package rather than just links.

[Aitch]

It IS a good idea - just that people have got used to the chaos....

You may need to categorize by Puppy version, or kernel number

Several people have offered to make databases, 'as it's easy'

yep! you can see the results....

Aitch

[nancy reagan]

Maybe it would help to ask moderators to make this page sticky for after a few weeks this topic will be sunk out of sight.

Yes one of the main features of puppy forum and help is that it is such a chaos, pity

[tlchost]

Several people have offered to make databases, 'as it's easy'
yep! you can see the results....

I was one of the folks that actually made an online database. It wasn't super easy. The downfall was that it required participation of folks to make entries about the versions, pets and SFS files.

The real downfall was that hardly anyone participated. I've used the same database design and software for other groups where it's been accepted, used and expanded.

Thom

[sidders]

I am one of those people who have not bothered,or forgot to post any sfs or pet on a database, although i did start with an sfs database.

There wont be a huge amount, but if we decide on a database i will go back through and post any i have done.

Sorry

[technosaurus]

If the entries were in a database or spreadsheet (google docs, zoho etc...) we could easily generate the wiki pages or add to the package manager or any number of things using a script

if the entries are:
category|petlink|description|imageurl|name|reserved_for?|

here is an example from the web desktop
CATEGORY
<li><a href="" title="Install Extra Multimedia Packages"><img style="border: 0px solid ; width: 24px; height: 24px;" alt="Install" src="index_files/multimedia24.png">Multimedia</a><ul>
PET_PACKAGE
<li><a href="http://www.puppylinux.ca/tpp/big_bass/REALPLAYER-11.pet" title="RealPlayer 11 - Media Player">RealPlayer11</a></li>

using sort, cut and sed the whole list could automatically be generated as a list (the css in the web desktop makes the lists into dropdown menus)

I could use it to quickly update the web desktop, generate a wiki page any number of formats really and quite possibly a petget addon (would likely need further entries similar to the petspecs in the reserved_for section)

[tlchost]

If the entries were in a database or spreadsheet (google docs, zoho etc...) we could easily generate the wiki pages or add to the package manager or any number of things using a script

But if no one adds them to a database, there''s no info to convert. I submit that there won;t be a lot of entries.

A central database might be a bit too organized for a free-wheeling community.

[technosaurus]

perhaps it would be better to just add something to the petspecs script so that it is automatically generated (it could assume that the user dumps all of their pets to their first-run configured main site - with the top directory stored in a config file and editable to add subfolders etc... ) Barry set it up to be able to do this kind of thing already.


For instance ttuuxxx's config file could have http://puppylinux.asia/tpp/ttuuxxx/ since that site is password protected there would need to be |user|password| parameters as well (for wget)

While mine would be http://puppy-development.googlecode.com/files/ with no username or password

The whole thing could be web-based and always up to date just by refreshing the page. (petget will automatically allow installation of pet packages from a webpage)

-- would this be the first distributed package management system or do others exist?

[gulk]

perhaps it would be better to just add something to the petspecs script

It might be a silly idea: when a pet has been generated, a pet specs is being included inside the .pet file.
How much of a burden would it be to actually create a copy outside the .pet?
Then all you have to do when submitting an entry in the "BPD" (Big Pet Database) is to upload this file along with whatever extra comments and link to the actual .pet.

The server's job would be to open this file and fill in the entries accordingly. Barry already did a pretty good job a categorizing the .pet using his pet generator scripts.


A an even sillier idea: is there a possibility for a server to actually recursively go through the forum and snif the pet files out? It could then download these files, extract the pet conf, categorize them and publicize in an orderly fashion.
Would it put too much burden on the forum's server? Also I have no idea at how much data we are talking about.

[technosaurus]

I actually already added a line in my script to echo it to a file in /root/.packages so that I can keep track of them - so yeah - that part is easy