Re: Backports and debhelper 3 for potato (was: Tool to generate an override file from packages?)

2001-09-25 Thread Christian Marillat
 "MH" == Marc Haber <[EMAIL PROTECTED]> writes:

[...]

> Is it _really_ that hard to get debhelper 3 for potato?

I did a backport 3 months ago (3.0.31). Only a little bug, you need to call
dh_perl with -d.

Except that, I never received any "bug report"

http://marillat.free.fr/dists/stable/main/binary-i386/index.html

Christian




Re: Backports and debhelper 3 for potato (was: Tool to generate an override file from packages?)

2001-09-25 Thread Daniel Burrows
On Tue, Sep 25, 2001 at 03:14:09PM +0200, Marc Haber <[EMAIL PROTECTED]> was 
heard to say:
> >Seems a lot less than most packages.
> 
> Make that "most packages I happen to backport". I am surely only using
> a small fraction of Debian, because I mostly run servers that don't
> have X or any nifty stuff installed, but I frequently encounter
> packages that need debhelper 3. I am not complaining about this,
> though. It is good to have new stuff developed.

  How many of them actually use debhelper 3 features?  I know I've been
guilty of gratuitously setting DH_COMPAT=3 now and then (and I know
dh_make defaults to it, which doesn't help)

  In at least some cases, changing that to DH_COMPAT=2 and maybe making a
few other small tweaks should get a decent backport.  It looks like the
only v3 features of interest [0] are globbing in config files,
automagic insertion of ldconfig by dh_makeshlibs, and automagic
conffile-tagging by dh_installdeb.  Depending on the package you're
compiling, these might not even matter..

  Daniel

  [0] from debhelper(1)

-- 
/ Daniel Burrows <[EMAIL PROTECTED]> ---\
|  "Of course you can't see the guards.  They DON'T EXIST!"   |
|  "Oh my god, we're surrounded!" "Run away, run away!"   |
|   -- Fluble |
\ News without the $$ -- National Public Radio -- http://www.npr.org /




Backports and debhelper 3 for potato (was: Tool to generate an override file from packages?)

2001-09-25 Thread Marc Haber
On Tue, 25 Sep 2001 13:42:59 +1000, Anthony Towns
 wrote:
>On Mon, Sep 24, 2001 at 09:08:32PM +0200, Marc Haber wrote:
>> Most sid packages have Build-Depends: debhelper 3 and DH_COMPAT=3 in
>> debian/rules.
>
>find pool/main -type f | grep '/.*/.*.diff.gz' | 
>   while read a; do zgrep -l DH_COMPAT=3 "$a"; done | 
>   sed 's,/[^/]*$,,' | uniq | wc
>933 933   13697
>
>find pool/main -type f | grep '/.*/.*.diff.gz' | sed 's,/[^/]*$,,' | uniq | wc
>   35423542   49523
>
>Seems a lot less than most packages.

Make that "most packages I happen to backport". I am surely only using
a small fraction of Debian, because I mostly run servers that don't
have X or any nifty stuff installed, but I frequently encounter
packages that need debhelper 3. I am not complaining about this,
though. It is good to have new stuff developed.

>In any case, though, wanting new packages to be written and uploaded,
>and then expecting them somehow to suddenly work on a potato box without
>any backporting doesn't make any sense either.

You're right. But backporting can be easy, and it can be hard. And it
is quite frustrating that a basic tool like debhelper is such a beast
to backport. debhelper depends on debconf-utils which is only in later
debconfs. And debconf's perl scripts use a lot of perl 5.6 features
like "our", and I don't think that there is any other way to get
current debconf running on potato than backporting perl 5.6, which is
_definetely_ something beyond my knowledge.

Is it _really_ that hard to get debhelper 3 for potato?

Greetings
Marc

-- 
-- !! No courtesy copies, please !! -
Marc Haber  |   " Questions are the | Mailadresse im Header
Karlsruhe, Germany  | Beginning of Wisdom " | Fon: *49 721 966 32 15
Nordisch by Nature  | Lt. Worf, TNG "Rightful Heir" | Fax: *49 721 966 31 29