Extend .info file

[Rich]

Hi nomer
I don't know whether my list has been accepted or whether members would prefer to try to adapt the freedesktop.org list.

[Guy]

Why not go with your list, but look at freedesktop.org and see if you get any ideas to improve your list.

[Rich]

Hi Guy
That is the approach I would like to take, though I will acknowledge that my opinion on the matter is biased.
I will be changing the  web  category to  internet and add web to the functions field as well as  chat.
I gave my reasoning on why I placed  office  under  editors  in reply #78, though I neglected to mention I'm
also trying to make it difficult for an application to fall under two different categories, not an easy task. I am
still interested in your opinion if you feel this should be changed.

@ALL: If there are any objections, please present them now so we can move forward.

[nomer]

@Rich
 I have no objections

@anyone
 How should *-dev.tcz, *-doc.tcz, and *-locale.tcz files be tagged? Should they inherit the tags from their parent? (When I say their parent I mean the package named *.tcz) Or should they have no tags? If we don't choose either ov those options then we'll have to create a new category or function, since these types of packages don't seem to fall under any of the chosen categories.
  Personally, I would prefer inheriting the "parent's" tags.
 

[vinnie]

I do not think we need a tag for local dev doc,
If the search for the tag works like  keywords, is included a partial search of the package name, that is equivalent to entering the package name (with any dev local doc) in a tag.

[Rich]

I have been giving that some thought, particularly because some extensions have separate dev packages and
some extensions include their dev headers and libs in the same package. In both cases the packager is free
to add optional tags, such as  dev  or  headers  for example.
If dev, doc, and locale are submitted separately, I think that using the same tags as the main extension is a
good way to go, since that way they would all show up on a search, and their name should make their
purpose obvious.

[roberts]

95 replies and little actual data.  This is what I am going to do....

Keyword is the concept that I seeded and some found useful.
I am going to force a Tags line into each and every .info file that does not have an existing Tags line.
Currently there are only 25 extensions that have a Tags line.

The forced Tags line will be based on the Description with many throw away words removed.

I have been testing this and it seems to be a good jump start that is needed to get this moving.
I want to try to get this in version 4.4.

Of course, any extension maker can update their .info files with better and more useful Tags.
Over time and with community involvement the Tags will improve.

[vinnie]

I am happy, as I'm concerned it could not have a better ending 

[roberts]

Forced tags inserted for tczs.

[Rich]

Hi roberts
I noticed something odd. In my extension:

Code: [Select]

Title: nvidia-96.43.20-3.0.3.tcz (TESTING)
Description: nvidia legacy video driver
Tags: nvidia legacy video drive
driver was changed to drive
In Arslans extension

Code: [Select]

Title: nvidia-glx.tcz
Description: NVIDIA Linux Drivers, Xorg driver.
Tags: NVIDIA Drivers Xorg driver
The word driver was unaffected.

    [EDIT]: I've already submitted a new info file, but this might effect other extensions.

[roberts]

Looks like the last char was chopped let me see if I can fix it.

[roberts]

Hang on regenerating and will repost shortly.

[roberts]

Fixed! 

You might have to delete /tmp/tags.db so that appbrowser/search.sh will re-download the updated tags.db.

[Rich]

Hi roberts
Thanks, looks good.

[roberts]

   Thanks for catching that!