← Back to team overview

software-store-developers team mailing list archive

Why we need debtags

 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jonathan

This morning we discussed the possibility of escalating debtags
publication in Launchpad. I promised to send you a summary of how
debtags would help Ubuntu Software Center.

When debtags are included in a source package, in any archive, Launchpad
should publish them in the archive's Packages.gz file. Currently it
ignores them. <http://launchpad.net/bugs/57418>

This blocks implementation of at least three features in USC.

Better categories

    Currently USC's categorization system is based on categories in
    .desktop files, and Section: values in debian/control files. Some of
    the categories are awkward, and several of them would be much more
    useful with subcategories (particularly "Fonts", "Office", "Sound &
    Video", "System", and "Themes & Tweaks"). The most practical way to
    improve this is to have accessible debtags.
    <http://launchpad.net/bugs/475773>

Maturity ratings

    It should be possible for people to filter software based on how
    much violence, horror, sex, degrading language, etc it includes.
    This requires packages to be rated, and for those ratings to be
    easily accessible without downloading the package. This could be
    implemented with debtags.
<https://launchpad.net/ubuntu/+spec/foundations-software-maturity-ratings>

Hardware requirements

    Especially for games, it is useful for people to know that software
    does not work with a particular kind of video card, or that it
    requires a particular amount of memory. This could be implemented in
    a machine-parseable way using debtags (so that, for example, USC
    could warn you if you don't actually have enough memory).

Thanks
- -- 
mpt
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4Bv7AACgkQ6PUxNfU6ecp5VgCffqCoG2ff24Z3bfkpQ3r15FXn
B+IAoNQQapCCzMADF3ka5YQHq+fRBHNC
=0Smq
-----END PGP SIGNATURE-----