[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Unofficial package tips



-----BEGIN PGP SIGNED MESSAGE-----

Thanks for you tips! But still some questions remain:

On Friday 28 February 2003 16:33, Bastian Kleineidam wrote:
> Native Package or not?
> ----------------------
> Short answer: don't make a native package.

Can you explain 'native package'? Did you mean 'binary-only' package by that?

> Be sure to provide a
> .orig.tar.gz before calling $(DEBUILD).

Hmm, dh_make is trying to do a similar approach. Why not use that way?


In addition i have some questions to the Depends section in debian/control:
${shlibs:Depends} is a nice feature, but i think for many packages/libraries 
it is way to strict, because it's always using the versions of installed 
packages which may not be necessary. So what's the best/common way to handle 
this?
It is possible to let ${shlibs:Depends} do its job and then lower that 
requirements? Or is this approach to dangerous and the one and only solution 
is always building on a 'clean' woody?

To be somewhat concret:
Currently i am building an inoffical package for k3b (for woody/sarge). I have 
KDE3.1 installed and am building against that. But k3b only requires KDE 
higher 3.x. So i wonder if i could lower the corresponding entry in the 
Depends section?

Thanks in advance
Henning

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iQEVAwUBPl+2WxbKLUjq1HQVAQFd2gf/dzZOyW1Ykz0hAOQXnPby6PZ9bBPZ2VFB
sq+IP1xRyR2qGLjy0FRTLBbo8/PX1qFhsOsmmzZOTGm/fp8i3s2iS57PYxJEfteS
01P0gAQ1jNIHHrBKlXC0Kkeo918fkJcbvqE2e0oJvH4mnpEnvrIKFMiMmDSfy9Yl
eXHOnWEgUwpeDtE62cRhlstN3ROAryz78ZAZpTJybTnjuC3IzjaKlrUigAs8Aie0
8a+IESyLaknZXF3+V6HSfkMpblv/95MAVcJCh8IaFi0f2KQZvUydazT/mhPVwKOB
AZgLyAfp+czt1IIrlc1QD2h4TfwEl9rQHotsl13fN9CuvLKllRKZNw==
=1mDA
-----END PGP SIGNATURE-----



Reply to: