[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#144046: general: Sections are not finely grained



On Mon, 22 Apr 2002 16:15:45 +0200
Javier Fern <jfs@computer.org> wrote:
> 	Users need a hierachical layout in order to find software.
> Keyword by themselves are not that much useful since they would be
> only appropiate to the language used. Several disadvantages:
> 
> 1.- more difficult to translate than sections
> 2.- are not organised hierarchicaly (sp?)
> 3.- difficult to represent graphically in a package-administration gui
> (sections are easily represented as trees).

Agreed. However, there's no reason why one can't conceivably have more
than on tree.

The tasks system is kind of like that. In fact, it's arguable that if
all packages belonged to at least one task, we would actually have a
hybird keyword/category system.

A package, gnome-calculator, could belong to the desktop task, the gnome
task, and the desktop-calculators task.

/me ponders...

What's it take to get a new task? Just a matter of adding a Task: field?
No other hoops?

If that's the case, then maybe the original poster would like to come up
with a relatively long list of "keywords" (really, just tasks).

The aforementioned gnome-calculator task could appear as the following
leaves in the tree:

desktop-calculators/gnome
gnome/desktop-calculators
desktop/desktop-calculators

Easy to present in a UI, and since a) the list of keywords (tasks)
needn't be a very small number, and b) a package can belong to more than
one task (have more than one keyword), it meets the original poster's
request.
-- 
________________________________________________________________________
\ David B. Harris, Systems administrator   |   http://www.terrabox.com /
/  eelf@sympatico.ca, elf@terrabox.com     |     http://eelf.ddts.net  \
\======================================================================/
/ Clan Barclay motto: Aut agere, aut mori.  (Either action, or death.) \
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Attachment: pgprQMl2buauK.pgp
Description: PGP signature


Reply to: