Re: r1771 - projects/med/trunk/debian-med/tasks
On Tue, Aug 18, 2009 at 03:46:50PM +0200, Steffen Moeller wrote:
> >> +Depends: autodocktools
> >> +Friends: mgltools-dejavu, mgltools-pmv, mgltools-utpackages, mgltools-vision, mgltools-volume
> > Enhanced-By: mgltools-dejavu, mgltools-pmv, mgltools-utpackages, mgltools-vision, mgltools-volume
> > What do you think?
> I'll go for it ... good to hear you like it (I was not sure).
Sure this is interesting information. I have no idea how to handle this information
for the moment but it is defintely interesting metainformation for a package. I do not
know a reasonable way to express it on the tasks pages, but it seems to be pretty clear
that these "Enhanced-By" packages should pop up on the bugs pages in case something
> While I was trying to rebuild the task pages myself, possibly finding the spot where to
> care for the Enhanced-By, I had found the update-all-tasks script for it, I was lost
> rather quickly. What I had found out I have now added to the script as a POD documentation
> (which I use to document all my scripts, but you may have other ideas). Could you please
> help that seed of a doc a bit more?
This is a perfectly valid critics. I added (hopefully) enough information to the
script that will make it clear enough that it's use on your local machine is very
limited if you are not running an UDD instance.
Every member of the Blends Alioth project can run it on alioth. If you are member
of the blends team you can go to
and (re)create the tasks pages. I should write some better doc but in short here
is some advise:
alioth$ cd /srv/alioth.debian.org/chroot/home/groups/blends
alioth$ ./tasks.py <your-blend>
creates the tasks page. Which blends are avialable can be seen by
alioth$ ls webconf/*.conf
It is allways interesting to have a look into the directory
where you can find information about packages which are just included in Debian
errors (:-(), and so on.
> To help spontaneous volunteers like me a bit, I would like to see the tasks pages
> themselves to give information about the scripts that have produced them. Like <tiny>This
> page was created by <a href="../trac/..">blends/webtools/update-all-tasks</a> with
> information from <a href=...>blends/projects/.../</a>.</tiny>
I'd consider this, yes. I think a good way is to increase the general Blends doc
a bit about this and just link to the actual paragraph.
> Would that be feasible?
You know the usual answer to this kind of questions, right. ;-)
Thanks for your interesting comments
Klarmachen zum Ändern!