Re: Blends and (astronomy) meta-packages
Hi Ole,
On Wed, May 13, 2015 at 03:24:00PM +0200, Ole Streicher wrote:
> Andreas Tille <andreas@an3as.eu> writes:
> >> Can I use the blends-dev tasks without actually creating a blends task
> >> but a "normal" metapackage?
> >
> > Before I can answer this question please define "normal metapackage".
>
> A metapackage that does not appear in the tasksel list.
Hmmmm, I think I need to recommend reading the Blends documentation.[2]
While the Blends term "task" is at some point related to the tasksel
system it is technically totally independent. To the contrary:
Unfortunately the Blends tasks are actually *not* in tasksel but should
at least at request (see #758116). So please make sure you understand
what we are talking about correctly since otherwise a misunderstanding
is unavoidable.
> My idea here is: I can generate a "tasks" file very easily since
> upstream provides a "registry.json" [1], which looks like
>
> {
> "packages": [
> {
> "name": "specutils",
> [...]
> "pypi_name": "specutils"
> },
> { [...] },
> [...]
> ]
> }
>
> which can be used to retrieve the list, canonically build the Debian
> package names (python-XXX; python3-XXX), request additional info from
> pypi, and then create the tasks lista from that.
Also here: I have no idea what exactly you have in mind but I have the
strong feeling that we are talking about different things when using the
term "tasks file".
> However, I would do that just for astropy-all, not for a "real" blends
> package yet. I want to move the decision if these tasks are
> debian-astronomy tasks to a later time.
I'd like to repeat: I'm positively convinced that the Debian Astronomy
effort would profit from a not too long delay to create the Blends
framework.
Kind regards
Andreas.
> [1] http://www.astropy.org/affiliated/registry.json
[2] http://blends.debian.org/blends/
--
http://fam-tille.de
Reply to: