[Soc-coordination] Report week 2, Redesign metapackage creation for Debian Blends

[Emmanouil Kiagias]

Hello,

This week:

This week was quite interesting. During Monday and Wednesday I finished I
first working instance of blend-gen-control:

* it now generates control(-c argument) or task-description(-t argument)
files
* if no specific architecture is provided to the script with -a argument
then it generates a file for each available  Debian architecture in the
format: <filename>.<arch>
* currently the generated files are saved locally either in
blends-gsoc/control folder or  in blends-gsoc/taskdesc folder.

As a reminder the code can be found here[0] also all the discussions in
debian-blends mailing list
On this code I got some feedback from my mentor (Andreas Tille) and I did
some changes:
* i fixed a wrong field in the generated task-description files and the
command line arguments[1]
* changed the query which gets all the available Debian architectures,
relevant discussions[2]

>From Wednesday up to today we tried to resolve the following issues:

The new blend-gen-control will replace the existing blend-gen-control and
thus it should fully imitate the latter's functionality. Writing the first
version of the new code we discovered that there was missing data from UDD
regarding the task files, so we also needed to add some extra headers in
the blend_tasks UDD table. My mentor made that fix[3], the relevant
discussion[4].

In addition to the above extra fields UDD fields regarding the tasks files,
we also discovered that we need to save somehow the alternatives
packages(we need them to proper generate the task description files): for
example if a field in a task file has Depends: package1 | package2 |
package3 <--- this relation is not saved in the current blends_dependencies
UDD table and thus we were thinking for way to solve this problem. The main
idea[5] is to add an extra table containing this info.

Next week(counting from half of today):

* deploy the new added blends_tasks UDD fields in the new blend-gen-control
* in case we add the new UDD table containing the alternative packages,
then deploy this table in the new code

Also we wait for responses on some open issues from this week.

* asked about the generated control file syntax on debian-mentor mailing
list[6], I asked first, waited a couple of days, then my mentor asked again
using more proper wording
* wait to find out if we need to include an extra field in UDD blends_tasks
table [7]

So for next week priority have the above issues. In case we don't create
the extra table containing the alternatives packages from task files(to
proper generate the task-description file) I will start writing the code to
keep track of the added/removed packages between Blend's releases.

PS: here I want to note that I am very happy to work with Andreas,(he is
very cooperative) I will try to keep up the same way (as Andreas) on
concentrating more on my code giving a better result for my project.


Kind regards

Emmanouil

[0]: http://anonscm.debian.org/gitweb/?p=blends/blends-gsoc.git;a=summary ,
https://lists.debian.org/debian-blends/2013/06/threads.html
[1]: https://lists.debian.org/debian-blends/2013/06/msg00028.html ,
[2]: https://lists.debian.org/debian-blends/2013/06/msg00035.html,
https://lists.debian.org/debian-blends/2013/06/msg00040.html
[3]:
http://anonscm.debian.org/gitweb/?p=collab-qa/udd.git;a=commitdiff;h=176cc3ef7f8b821c54047af57c234d696ae8bd88
[4]: https://lists.debian.org/debian-blends/2013/06/msg00029.html
[5]: https://lists.debian.org/debian-blends/2013/06/msg00031.html

[6]: https://lists.debian.org/debian-mentors/2013/06/msg00255.html,
https://lists.debian.org/debian-mentors/2013/06/msg00296.html
[7]: https://lists.debian.org/debian-blends/2013/06/msg00039.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/soc-coordination/attachments/20130628/3b064123/attachment-0001.html>