[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#703402: PTS: link to the blends website for packages involved in blends

Hi Paul,

On Mon, May 27, 2013 at 01:06:14PM +0800, Paul Wise wrote:
> > IN fact I'm considering a not yet used update mechanism in UDD - perhaps
> > some commit hook or so which sounds more apropriate in the Blends
> > metapackage case.  A daily import (as usual in UDD) does not make much
> > sense because over several days the content remains static.  But at some
> > points in time there are several changes on one day.  I need to think
> > about this.
> Long term I think we want to move Debian infrastructure towards some
> sort of realtime messaging system like fedmsg, AMPQ etc. So dak would
> emit events, UDD and other QA stuff would listen to those events and
> update themselves in realtime.

Sounds quite interesting.

> > This does not sound fully convinced.  Do you see any drawback in this
> > historical fact?
> Just that the strings on the PTS are very long when they include the
> blend name, I worked around this by just including task names. With
> the tasks from tasksel having long names too, I might need to do some
> sort of shortening method.

I have introduced a 'title' field.  Please check again


It now creates two different JSON files that should contain all needed
information.  Please tell me if something might be missing.

> > In fact most Blends do create a tasksel package as well (debichem-tasks,
> > med-tasks, etc.)  I had the idea that not only packages matching 'task%'
> > in their name should match the query but rather those that depend from
> > tasksel package.  I'll come up with some suggestion for a JSON data file
> > soon.
> Great, thanks.

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.

Kind regards



Reply to: