Puppy Linux Discussion Forum

L18L

filtered packages that
- are already in categories.dat
- do not have an entry CATEGORIES= in .desktop (they exist!)
and sorted by category

remaining 1765 packages

The first one:

technosaurus · Joined: 18 May 2008 Posts: 3843

@L18L does it look like we need to do something like:
echo Package=$PACKAGENAME >> package/.../*.desktop
so we have a basis for determining the package name, or are most fairly straight forward

I am stuck in windows mode until I finish my programming languages project, so I can only give guidance right now, but if you open up jwm_menu_create (from jwm_tools) all of the language is there to generate all subcategories, all that needs to be done is:
set the subcategories variable to true (i forget the exact var name)
change the directory path from /usr/share/applications to the appropriate dir. remove the unneeded jwm markup
change the output to just give the format that Barry needs, which is ???
(p.s. my sub-category names may slightly differ but that is easily fixed by humans pretty quickly)
I assume that output could be:
category|subcategory|packagea packageb

(note to self: may need tolower so we can use strstr instead of needing strcasestr which is slower)

L18L

Let's start with Fun Laughing

BarryK · Posted: Thu 15 Nov 2012, 21:43 Post subject:

L18L,
Ha ha, 'dosbox' a game Laughing

Well, yesterday I did a test Precise build, and the 'debdb2pupdb' utility created this package database entry for dosbox:

BarryK · Posted: Thu 15 Nov 2012, 22:06 Post subject:

L18L,
while putting pkgs into categories.dat, or preparing to do so, if you think that there is a bunch of packages that really should have another sub-category, we can easily add that.

For example, maybe many of the top-level categories should have a "utility" sub-category. For example:

L18L · Posted: Fri 16 Nov 2012, 06:24 Post subject:

sunburnt · Joined: 08 Jun 2005 Posts: 4006 Location: Arizona, U.S.A.

While you`re writing specialized scripts to parse the desktop files...

Why not generate an app. library dependency data base with ldd.?

I`ve said that statistics on library usage is a key item for O.S. design.
Puppy`s installed libraries are probably a good list of common ones.

But many apps. need more, so which libs. are only used 1 or 2 times?

Include the commonly used libs. in Puppy or make an add-on SFS file.
The rarely used odd libs. just include with the apps. It`s good design!

# Sorry for stepping on your thread Barry... The thought struck me. Wink

pemasu · Joined: 08 Jul 2009 Posts: 5169 Location: Finland

Is this finding relevant to the packages categories work:
http://www.murga-linux.com/puppy/viewtopic.php?p=665179#665179

seaside · Joined: 11 Apr 2007 Posts: 835

While there are some perl and python programs to convert a deb file to a tar.gz file, I was surprised to find that just using linux tools was actually faster.

I found that the tar file starts at exactly 60 bytes offset from the header "data.tar.gz". (At least in the 6 deb files I tested). So here's an extractor for *.desktop files.

L18L · Last edited by L18L on Wed 21 Nov 2012, 07:06; edited 2 times in total

All data and scripts are in one directory.

fill_categories.tgz came a little later than the pictures

L18L · Posted: Tue 20 Nov 2012, 17:16 Post subject:

pemasu · Joined: 08 Jul 2009 Posts: 5169 Location: Finland

It has been fixed with latest woof commits.

http://www.murga-linux.com/puppy/viewtopic.php?p=665483#665483

L18L

technosaurus · Joined: 18 May 2008 Posts: 3843

I went through the desktop files looking for any gotchas and to see if it would be feasible to just include the icons but noticed that:
(41) apps use svg icons (not supported by jwm) ... need a wrapper to convert to png and modify desktop file on install
(15) specify no icon