Hi Andreas, On Tuesday 08 April 2008 09:14, Andreas Tille 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". Ok, thanks for the explaination. All the above happens on the developers machine, before uploading the package, right? > 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? Honest answer: I havent read that since before Merida. :-/ > > 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. I wonder why this is run on the buildd. regards, Holger Currently I'm offline otherwise I'd read the cdd-dev-doc now.
Attachment:
pgpJ_mZxWKo4j.pgp
Description: PGP signature