On Mon, May 27, 2013 at 8:08 PM, Andreas Tille wrote: > Sounds quite interesting.
http://wiki.debian.org/SummerOfCode2013/StudentApplications/SimonChopin http://lists.debian.org/20130425115056.21764.39271@mithrandir > I have introduced a 'title' field. Please check again > > > http://anonscm.debian.org/gitweb/?p=blends/website.git;a=blob;f=misc/pts/taskinfo-example.py > > It now creates two different JSON files that should contain all needed > information. Please tell me if something might be missing. Looks good, here are some examples, I would be interested in your thoughts. http://packages.qa.debian.org/~pabs/g/gromacs.html http://packages.qa.debian.org/~pabs/g/gimp.html http://packages.qa.debian.org/~pabs/g/ghemical.html Let me know if you want some other packages rendered or any changes made. I changed the wording to tasks instead of blends since it is more task-focused. When there are more than 5 tasks, I currently display numbers instead. Maybe where there are more than 5 tasks I should list just the blends instead of individual tasks? > After a second thought things are not that simple as I've thought in the > first place. While it is easy to detect what packages do contain > tasksel input the real dependencies of the tasks are hidden *inside* the > package and not available in UDD. In other words: To create a link > from a package to the task it might belong to we need to create a new > UDD importer that parses those tasksel control files. Hmm, ok. -- bye, pabs http://wiki.debian.org/PaulWise -- 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/caktje6fudadntkb-mwzdkpqsuzo9t0tx4sajb2ds4ry2c-l...@mail.gmail.com
