[Debtags-devel] wishlist

Justin B Rye jbr at edlug.org.uk
Fri Sep 16 11:21:52 UTC 2005


I'll start by documenting some "Tagging Hints And Tips" - the
following tools have been particularly useful for working out what
unfamiliar packages are all about.

* apt-cache (obviously; but nb "apt-cache rdepends")
* apt-file ("does it put anything in /usr/bin?  In init.d/?")
* debman, in debian-goodies ("what does its man page say?")
* surfraw (instant lookups of packages.debian.org/foo)

----------------------------------------------------------------------
WISHLIST

Extra tags for consideration.  Please object to any that seem
unnecessary!

Tag: field::linguistics
Description: Linguistics

 (Low priority; morphological analysis, speech-synthesis, IPA fonts) 

Tag: hardware::storage:floppy
Description: Floppy disk
Tag: hardware::input:keyboard
Description: Keyboard
Tag: hardware::scanner
Description: Image-scanning hardware

 (Each of these would make particular kinds of package much more
 recognisable.  But this facet may be a slippery slope.)

Tag: langdevel::octave
Description: GNU Octave
Tag: langdevel::prolog
Description: Prolog

 (A couple of dozen development packages each; the octave one might
 not be needed, since there's an obviously-named metapackage)

Tag: protocol::snmp
Description: Simple Network Management Protocol
Tag: protocol::ssh
Description: Secure SHell

 (As mentioned; we have ::sftp, and ::corba, and ::fidonet, but no
 ::ssh?) 

Tag: made-of::data:man
Description: Manuals in nroff format

 (Useful to tag the few content-packages made entirely of manpages,
 but also the many that are HTML+info+man or similar)

Tag: uitoolkit::fltk
Description: FLTK - Fast Light Toolkit user interface

 (A couple of dozen, though it's hardly a very distinctive UI)

Tag: works-with::network
Description: Network

 (From previous thread.  This could usefully be attached to
 network-capable games, remote as opposed to local login-mechanisms,
 etcetera, and see below on redundant network:: tags.) 
----------------------------------------------------------------------
HITLIST

Tags that can be moved/eliminated to reduce duplication, or maybe
just have their descriptions modified to clarify the distinction:

admin::configuring vs use::configuring
admin::login vs use::login
admin::monitoring vs use::monitoring
	In each case there could be a distinction in terms of
	whether it's the sort of configuring/login/monitoring that
	requires an admin password, but it's not very clear.

filetransfer::
	This whole facet is made of protocol:: dupes (without on the
	other hand managing to cover uucp, peer2peer etc).

mail::imap vs protocol::imap
mail::pop vs protocol::pop
mail::smtp vs protocol::smtp
	The mail:: facet can afford to leave the protocol names for
	the dedicated protocol:: facet to handle.

network::firewall vs security::firewall
	Perhaps the network:: one should be replaced by a
	"network::filters", to cover spamassassin, procmail(?),
	junkfilter, dansguardian etc as well as firewalls.  Or a 
	general use::filtering, but of course that would affect a
	huge number of text-filtering packages...

network::configuration vs admin::configuring vs use::configuring
network::scanner vs use::scanning
	If we're adding a works-with::network, these become even
	more redundant.
-- 
JBR
Ankh kak! (Ancient Egyptian blessing)



More information about the Debtags-devel mailing list