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

Re: Tasks pages (close to) fixed; Bibref does not seem to be updated automatically



On Tue, Feb 21, 2012 at 11:53:18AM -0500, Yaroslav Halchenko wrote:
> e.g. ATM we have
> 
> $> cat brian/debian/blends
> Source: brian
> Tasks: debian-science/neuroscience-modeling
> Depends: python-brian
> Published-Authors: Goodman D.F. and Brette R.
> Published-Title: Brian: a simulator for spiking neural networks in Python
> Published-In: Front. Neuroinform
> Published-Year: 2008
> Published-DOI: 10.3389/neuro.11.005.2008
> 
> for brian (binary pkg python-brian)

OK.  Now I also understand blends-inject a bit better. :-)
 
> I envisioned getting
> 
> debian/upstream  with
> 
> Reference-Author: Goodman D.F. and Brette R.
> Reference-Title: Brian: a simulator for spiking neural networks in Python
> Reference-Journal: Front. Neuroinform
> Reference-Year: 2008
> Reference-DOI: 10.3389/neuro.11.005.2008

You can take for granted that making this possible is high on my
priority list.

> while in debian/control add after 
> 
> Package: python-brian:
> 
> X-Blend-Depends: debian-science/neuroscience-modeling
> 
> Since you will be taking care about parsing information from debian/upstream,
> there will be only tiny job for blends-inject -- to inject the Depends entry
> into the corresponding tasks pages
> 
> does it make sense?

I agree this makes sense (even if I would prefer a s#/#,# to comply with
the usual komma separated syntax in debian/control files.  However I have
no good idea about implementation.  The only real consequence I would see
for the moment is, that it might make sense to prefer the proposed layout
for the Git repository of debian/upstream files as

    <package>/upstream

when doing so we could also add

    <package>/control
    <package>/copyright

to parse these data as well.  Claiming that I would implement this
soonish would be trigger false hopes - but if you want to deal with the
implementation I'd be happy.

Sie note:  Another idea popped into my mind how I could deal with "lazy
blends maintainers" like Games team for instance who do simply nothing
at all and leave me alone with stuff I do not feel competent for (like
sorting games into categories).  My idea was to inject packages based on
DebTags into the tasks files (or ... <some more advanced but unrelated
idea>).  So injecting data into tasks files automatically is some issue
I'm generally interested in.

Thanks for your input

    Andreas.

-- 
http://fam-tille.de


Reply to: