Hi Paul, On Sun, May 26, 2013 at 02:06:06PM +0800, Paul Wise wrote: > On Sun, May 26, 2013 at 3:34 AM, Andreas Tille wrote: > > > I have prepared a Python script that creates JSON output with the > > relevant data from UDD. Please check out > > Thanks. Could you move that to a CGI running on udd.d.o though?
I need to find out how to do / where to place this because I did not yet dealt with CGIs on udd.d.o but once your specification (see below is fullfilled I can do this if it helps). The only thing I'm wondering whether a CGI script should always run the query itself. It would be way more efficient to drop the result somewhere and just deliver the content via CGI because the usual change of the data is either once per day or once per change in the blends tasks files (I did not yet decided how I might trigger the importer). > > and run it from alioth. Please let me know if you need any other > > information. Remark: The Blends data are not yet updated via cron job > > in UDD. This needs to be organised once the data has proven to be > > useful. > > I've implemented a preliminary version based on what you provided and > generated a page for gromacs: > > http://packages.qa.debian.org/~pabs/g/gromacs.html > > However, the data lacks some essential elements. > > I would like to be able to generate this: > > <a href="http://blends.alioth.debian.org/debichem/tasks/molmech#gromacs" > title="DebiChem Molecular mechanics packages">molmech</a>, > <a href="http://debian-med.alioth.debian.org/tasks/bio#gromacs" > title="Debian Med Biology packages">bio</a> I can add this easily but I think it would be very redundant to add the full URL string for every single package in the JSON data set. Would you think it makes sense to deliver an additional JSON data file [{"blend": "debichem", "tasksurl": "http://blends.alioth.debian.org/debichem/tasks/"}, {"blend": "debian-med", "tasksurl": "http://debian-med.alioth.debian.org/tasks/"}, ... ] > <a href="http://blends.alioth.debian.org/">blends</a> > > The JSON only has this: > > {"component": "main", "dependency": "d", "task": "molmech", "blend": > "debichem", "package": "gromacs"} > {"component": "main", "dependency": "d", "task": "bio", "blend": > "debian-med", "package": "gromacs"} > {"component": "main", "dependency": "d", "task": "chemistry", "blend": > "debian-science", "package": "gromacs"} > > It needs at least: > > The URL of the task. See above. > The title of the task. I would think about to what export I might add this information in case you agree to reduce the redundance a bit by providing two different data files. > Also, I'm surprised to see the blend name is debian-med when the task > meta-packages in Debian are med-* The prefix of the metapackages can be differnet from the Blends names. In fact if I remember right DebiChem is the only one were the prefix fits: Debian Med: med-* Debian Science: science-* Debian Edu: education-* ... > It would be interesting to also import tasks from tasksel too if that > is possible. You mean tasks that are in tasksel without using the Blends framework? Hmmm, I'm not aware that this data is in UDD in some structured manner. However, we could try with SELECT depends, recommends, suggests from packages where package = 'task-gnome-desktop' ; depends | recommends | suggests ----------------------------------------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------- tasksel, task-desktop, gnome-core, network-manager-gnome | gnome, libreoffice-gnome, libreoffice-evolution, gimp, synaptic, iceweasel, libreoffice, libreoffice-gcj, libreoffice-help-en-us, mythes-en-us, hunspell-en-us, hyphen-en-us | If this is what you want to use (probably without the "Depends: tasksel") I could probably create a similar JSON file. As title we could use udd=# SELECT description from packages where package = 'task-gnome-desktop' ; description --------------------------- GNOME desktop environment Just tell me if this would be helpful and I could do this as well. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org