On Tue, Mar 31, 2009 at 11:13:11AM +0200, Carsten Hoeger wrote:
On Mon, Mar 30, Paul Elliott wrote:
But it is not true. To see this look at the peless project:
+https://build.opensuse.org/package/show?package=peless&project=home%3Apelliott1 +1
It IS true. It's just that the debian package metadata is contained in the *.diff and *.dsc file(s). It's NOT contained in the *.spec file(s). That's what I wanted to make clear.
Well the way I read it, it is giving the impression that you must have files of the form debian.control, debian.rules, ect in the Files section. Now the info in these files has to be there somehow, directly or directly, but it can be concealed. In the .diff.gz file. For some people it is more convenient to work with true debian source packages. For example, I am the upstream source for the peless package. It is actually a package maintained by others in the official debian repository. If I want to check that my upstream changes I have made to the source do not require any changes to the debian files, I install the existing debian source package, and then do a "uupdate" with my new upstream source. That is what the debian people will do when I tell them about my upstream changes. I then upload the resulting debian source package to the build service and check that it builds correctly. When this happens I know that my package does not require any changes to the debian build files, or I know what those changes are. I then can report to the debian people what changes my new release will require if any to the debian build files. I never mess with files of the form debian.rules ect on the build service. Instead I always deal in true debian source packages. The documentation does not make it clear that this is an option unless you read it with a microscope. -- Paul Elliott 1(512)837-1096 pelliott@BlackPatchPanel.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117