Hello Andreas
between the latest release and the current release of a blend that lists addedand removed packages per task. From a previous older discussion we had you gave me the following example of entry log(in this example we use Debian med blend):
----------------------------------------------------------------
debian-med (1.14) unstable; urgency=low
* Changes in metapackage dependencies - med-bio:
added: package_a, package_b, ... removed (optional): ...
- med-... * New metapackages
- med-...
My one question here is how you define a release? I suppose you use VCs tags. If that's true then we can do it the following way:
*For blends that are maintained in svn:
We can get the revision numbers of all the existing tags. Then having the revisions we can use them with svn diff /path/to/blends/task/file -r revision1:revision2 , parse the diff output and keep the added and removed packages per task per blend etc.
*For blends that are maintained in git:
The idea is the same with the svn, git is quite handy with the tags and we can use them with git diff to track the added/removed packages in a task between tags releases.
Apart from the tags we can use straight svn commit revision number(or commit hash in git) for the latest and a/the previous release to get the differences. So this method can be called (eg can be called as a svn/git hook maybe?) every time you tag/commit a new release for a blend. Anyway the changelog entry is indepedent from the main goal of the project so we can come back to it anytime.
I am looking forward to start coding for the project :-) . Any other ideas, feedback or features are more than welcome.
Have a nice weekend.
Kind regards
Emmanouil