On Mon, 7 Jul 2008, Chris Walker wrote:
So the purpose of the meta package is to list packages that a
physicist will use, and not to classify physics packages. That makes
sense - and I'd previously missed that.
I can then ask my sysadmin to install the physics metapackge safe in
the knowledge that I'll have most of what I need.
This exactly is the use case. I - as a physicist by pÃrofession - need
some tool to support my colleagues who are doing microbiological research
in a medical institute. The easiest way to do this is
apt-get install med-bio .
I haven't added scilab as it is in non-free (though perhaps it should
be added).
Well it is added as Suggests and the cdd-dev tool just turns non-free
packages into suggests automatically - so a Depends would be safe here.
It will be listed in the first section for the moment but I plan to
rate Depends / Recommends higher in the future (some "dark green" packages
on top followed by "light green" Suggests).
diff --git a/physics b/physics
Applied.
http://cdd.alioth.debian.org/science/tasks/physics.html mentions
debtag field::physics but doesn't provide a hotlink. Is there a way of
doing this (I couldn't work one out)?
Would you think linking to
http://debtags.alioth.debian.org/
is fine? The problem is the description text of the task is turned into
the long description of the science-physics package and we should not do
highly sophisticated URL stuff here. The tool which creates the web page
turns everything that "smells" like an URL into a link. I have no idea how
to specify field::physics in the URL - these pages are highly JavaScript-ish.
And you can categorise your favorite packages at
http://debtags.alioth.debian.org/.
Perhaps I don't understand debtags well enough, but I think it would
probably be useful to have more precise tags than field::physics -
though I've yet to work out what tags would be appropriate.
Sounds reasonable - talk to the debtags team. We did so for biology as
well ...
PS there isn't a field::engineering tag on
http://debtags.alioth.debian.org/ either - though it is referenced in
the engineering metapackage.
Currently there is no debtags - metapackage relation currently - but
it might make sense to approach this. I could imagine DebTags as
extended source of information about packages we might have forgotten
to specify in the tasks files. (I do not really trust that every package
is properly tagged to take DebTags database as replacement for the
meta package tasks file - moreover the tasks files also contain information
about not yet included projects - so DebTags can not be a full replacement).
Kind regards and thanks for your input
Andreas.
--
http://fam-tille.de
