On Mon, 7 Apr 2008, Holger Levsen wrote:
I thought the tasks files are created manually
Yes, the tasks files are created manually.
by running "make dist" and then commited to svn?!
No, not at all. "make dist" creates debian/control out of the manually created tasks files respecting the availability of the packages mentioned in the tasks files in the respective target distribution. This is the mechanism as it is used for years in the Debian Edu packages.
Or is this used when running "make dist" and the changelog is not directly used by the build scripts?
When saying "make dist" the changelog is used for two purposes: 1. Obtain the version number of the tarball that should be created. 2. Obtain the target distribution that should be verified for the packages that are available in the dist. Packages that are available will be turned to "Recommends", those who are not available inside "main" of the target dist are turned to "Suggest". I hoped this becane clear in http://people.debian.org/~tille/cdd/ap-DevelDescription.en.html#s-cdd-dev but obviousely it did not. Any patch to enhance the doc to make this clear?
Then I still dont understand why the commited value matters..
There is no distribution "UNSTABLE" and thus no distribution where you can verify that the packages in the tasks file really exist - which is the main purpose of auto generating the debian/control file. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]