[kde-linux] linux source packages howto

[Donatas G.]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Werner Joss wrote:
> Am Donnerstag, 3. August 2006 16:56 schrieb Donatas G.:
>> Where could I read about the conventions of making linux source packages?
> 
> well,
> there are obviously more than one commonly used build systems/conventions :)
> one often used is autoconf/automake - see 
> http://www.openismus.com/documents/linux/automake/automake.shtml
> - autoconf/automake has been the kde-buildsystem for years, but kde switches 
> to cmake for kde4...
> http://dot.kde.org/1151688350/
> 
> werner

OK, I see :) , let me explain more...

I have made a few Kommander scripts, that I intend to be useful for
others. I would like to put them into a "source package" that could be
easily installed by others, and also produce "binary packages" for the
distro I am using - debian.

For now I am doing debian packages the hard way: I produce the whole
tree of directories with files in their proper dirs and then build a
package out of that directory tree. But the usual way of building debian
packages is not that. There are debian (and rpm, I guess) tools that
take the source package and, based on the provided compiliation and
installation info and the distro specifics make a package for a
particular distro.

But there is a standard source package that all of the different
programs act on.

In my packages I do not compile anything - maybe just the translation
files. So, how do I arrange „source package“ so that debian and other
package building tools could act upon?

Donatas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRNNJzvDtAb8AVdgrAQIxhgQAlFey6sPGN+6eXqKdLo7LJXFlw3PkJ1Mn
8UV/yrMS3IwQPVrsJCY5uaGG3+HFq5z4zBhjVonE48hGFlTW1erwEicoVbn9HGax
8eOIeeaCc8vgJGzFfHFFiKvhplFoPtBwh6chyz6mTJjQ48QiJ8Q1bfjcj4l5xhqz
2/J4VBtT2dk=
=L54w
-----END PGP SIGNATURE-----