Am Dienstag, 17. Juli 2007 11:20 schrieb Roland Wolters:
Once upon a time Stephan Hermann wrote:
You shouldn't build a debian package without
knowing anything about
debian, the same applies to any other distro.
Who said I don't know anything about the distro?
Anyway, knowing something about a distribution like file system and service
handling is still something totally else compared to building packages.
What I wanted to say is, e.g. init scripts are different regarding the
differnet distros, post(un)inst and pre(un)inst are handled differently, init
services are triggered differently etc. this has to be known. (e.g.
chkconfig, insserv, update-rc.d, or the new Upstart project from Ubuntu)
After all, e.g. for Debian/Ubuntu for every executable there needs to be a man
page. If it's not there from upstream you have to generate one as packager,
afaik this rule is not given for most rpm based distros, please correct me if
Or regarding copyright licenses...the debian/copyright file is quite different
regarding the information it needs, then that what we provide in the rpm spec
So if you want to provide e.g. some "third-party" packages for Debian/Ubuntu,
these infos are essential, as well the signed source package. Many people
checking those things, without those infos they won't install a package at
all or using official backport repositories (e.g. ubuntu is providing
official backport repositories, debian has some semi-official ones)
Therefore, as I see the buildservice, which is very "IMHO", the opensuse
buildservice can help to build several binary packages for several distros,
rpm and deb based, but we (as the users of the build service) should follow
and honor the different rules of the different distros.
Or you can tell some people what you want to
package and they create a
debian package for you, including the debian/ dir.
Of course, but I can do that without OBS as well. I thought OBS bridges the
gap between deb and rpm distributions a bit by making it easier to build
for both types, but I was wrong there at least for the current situation.
Right. OBS can't "cross create" package build descriptions for different
distros, even rpm based distros are different.
The funny thing about this is, that one idea was (when I remember correctly my
chat with Adrian last year) that there is a plan to create something like
this with xml written build description (not the build configurations for
different distros on the obs server itself).
I could imagine that it is possible to do that. Finding out the similarities
for a global xml package build description and handling the differences with
different xml namespaces. Creating the different files for different build
environments with xslt then is just a matter of time and testing ;)
At least that would be a feature what I would like to see in the future, even
thinking about Mark Shuttleworths talk during Akademy 2007 (Listen and Watch
it here http://home.kde.org/~akademy07/videos/1-06-Keynote-Shuttleworth.ogg
or to spare bandwidth you can find it as well on my server:
eMail: sh(a)sourcecode.de Blog: http://linux.blogweb.de/
OSS-Developer and Admin