Hi!
* Georgi Chulkov <g.chulkov@jacobs-university.de> [080331 22:35]:
> I have almost managed to package my first library. :) But one problem remains:
>
> "dpkg-buildpackage -rfakeroot" always builds a native package. I would like to
> build a non-native one, but I don't know how.
You need to rename the source-tarball. libnonsense_0.1.0.orig.tar.bz2
should do it.
> What I do currently is take the upstream archive
> ("libnonsense-0.1.0.tar.bz2"), extract it, pur the debian/ directory inside
> the extracted directory, and run dpkg-buildpackage in the latter. I end up
> with:
>
> libnonsense0_0.1.0-1_i386.deb
> libnonsense_0.1.0-1.dsc <- some kind of description file, but who uses
> it?
It is used to combine different files of a source package, e.g. the
orig.tar.gz and the diff.gz (which you'll get, if you build a non native
package).
Application using it, are for example dpkg-source, pbuilder and dget.
> libnonsense_0.1.0-1_i386.changes <- what is that?
A file summarizing the changes your package would do to the archive:
Listing all the files you would upload (note for example, that
orig.tar.gz won't be included by default, if you upload a package
revision >1).
> libnonsense_0.1.0-1.tar.gz <- why is this created at all and is it
> different from "libnonsense-0.1.0.tar.bz2" other than by name and compression
> format?
Because dpkg-buildpackage thinks you are building a native package, so
this tar.gz contains the upstream sources as well as your debian
directory. Looking at how strange some upstreams name their tarballs:
How should dpkg-buildpackage know, which file is the original tarball?
> Thank you for your help!
You are welcome.
BTW: Did you read the new maintainers guide [1]? I'm pretty sure it's
covered there... http://www.debian.org/doc/maint-guide/
Yours sincerely,
Alexander
--
http://learn.to/quote/
http://www.catb.org/~esr/faqs/smart-questions.html
Attachment:
signature.asc
Description: Digital signature