Hi Paul,
that's an interesting feature I have not thought about - thanks for
bringing this up.
On Tue, Mar 19, 2013 at 04:33:41PM +0800, Paul Wise wrote:
> For packages that are involved in a Debian Pure Blend, it would be good
> if the PTS were to link to the blends site from the links on the right.
>
> <a href="...">jr</a>, <a href="...">games</a> <a href="...">blends</a>
For the moment I see some problem here because a single package could
perfectly be part of more than one Blend as well as part of more than
one task of a single blend. For instance consider gnuplot in Debian
Science:
$ grep gnuplot projects/science/trunk/debian-science/tasks/*
projects/science/trunk/debian-science/tasks/nanoscale-physics:Depends: gnuplot,
grace
projects/science/trunk/debian-science/tasks/robotics:Depends: octave, gnuplot
projects/science/trunk/debian-science/tasks/viewing:Depends: gnuplot, grace,
gri, labplot, graphviz, pyxplot, plotdrop, qtiplot
or gromacs in DebiChem and Debian Med:
$ grep gromacs projects/{debichem,med}/trunk/{debichem,debian-med}/tasks/*
2>/dev/null
projects/debichem/trunk/debichem/tasks/molmech:Depends: gromacs
projects/med/trunk/debian-med/tasks/bio:Depends: gromacs
projects/med/trunk/debian-med/tasks/cloud: gromacs,
So putting a binary package into a task is not a strict (=exclusive)
categorisation because one binary package could serve several different
purposes. I have no idea whether this can be reasonably reflected in
PTS.
> Requirements on the blends side are a machine-readable mapping between
> the blends, their URLs and the packages that are available in them.
This can be approached and I could perfectly imagine to put the content
of all tasks files into an UDD table if this might simplify things. But
also here we should choose the table design apropriately: You can either
give the Blend / Task preference like
create table blends (
blend text,
task text,
pkg text
)
or you could add an array valued field to the packages table mentioning
...
blends text[],
blends_tasks [], -- task name needs to be prefixed by blend name
...
to reflect the nature of the tasks (and I'm in preference of the first
table layout because the second is more than hackish).
> The
> blends sites appear to be binary package oriented, we would probably
> also need anchors named after the source packages to link to?
They are:
http://debian-med.alioth.debian.org/tasks/bio#gromacs
to stick to the later example of gromacs in Debian Med.
Kind regards
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-qa-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130319094735.gg13...@an3as.eu
