Re: [GSoC] blends-gen-control hints (Was: blends-dev, gsoc 2013)

[Andreas Tille <andreas@an3as.eu>]

[Petter, please read below about packages.txt and avoidpackages.txt]

Hi Emmanouil,

On Thu, Jul 25, 2013 at 09:57:01PM +0300, Emmanouil Kiagias wrote:
> > Seems it's time now to create a complete orig source tarball to build the
> > metapackages.
> >
> I forgot to ask you, what about the task-description files? Are we going
> to keep multiple taskdesc.<arch> files?

I guess yes, we need the different taskdesc files because tasksel has no
better mechanism.  The alternative would be that you do some postprocessing
in the rules file according to some markers you could leave in a similar
way as in the control file.  So either you keep what we have and just install
the proper file in the rules file or you do some magic like

   grep -v "!<arch>" tasksel | sed 's/\[.*\]//'

or something like this in the rules file to strip some tasksel template
for final use.

> In order to complete orig source tarball to build the metapackages, I need
> to imitate the current blends-devtools right?

I think they do not really need much change - but reviewing might
definitely not harm.

> That means for example I am
> going to use the files blends/devtools and adapt them to the new code.
> Which other files do I need?

I have not fully made up my mind but IMHO the diff to the current
blends-dev should be not very large.  It just processes an existing
orig.tar.gz tarball and the main work to create this was switching to
UDD.

> Also in the current blends/devtools/Makefile you generate the
> 
> * packages.txt : these should be the available packages we have?
> * avoidpackages.txt : the avoided package.

That's part of the orig.tar.gz creation.  We should ask Debian Edu
people if these will be needed in future.  I totally forget about these
because I'm not using these.

> Am I also going to generate these files too?

Petter might answer this question.

Kind regards

       Andreas.

-- 
http://fam-tille.de