Forwarding information that failed to be CC'd to the bug report.

-------------------- Start of forwarded message --------------------
Message-ID: <710052.87607...@web26505.mail.ukl.yahoo.com>
Date: Mon, 2 Aug 2010 16:21:43 -0700 (PDT)
From: Mark Hobley <markhob...@yahoo.co.uk>
Reply-To: markhob...@yahoo.co.uk
Subject: Re: Bug #546445: A revised m4sh.m4 may be ineffective
To: Ben Pfaff <b...@cs.stanford.edu>
In-Reply-To: <87sk2w22bn....@benpfaff.org>


--- On Mon, 2/8/10, Ben Pfaff <b...@cs.stanford.edu> wrote:
 
>     Why are you modifying
> /usr/share/autoconf/m4sugar/m4sh.m4?

It doesn't work properly on my ash shell, (there are some constructs that 
autoconf uses, that are not considered), and I have problems sharing scripts 
between machines, because autoconf makes decisions based on the test machine, 
which do not apply to the target.

>     Local changes to these .m4 files are not
> anticipated in the
>     packaging (and that's why it doesn't work).

Really, this is a bad design. If the sources are newer than the frozen files or 
the cache, then the frozen files or cache should be updated. (We could use make 
here.)

> please let me
> know so that I can close the bug.

I have forked this package, and I am making appropriate modifications to the 
fork. I would just forward the bug information upstream, then close the bug. 
(The problem only affects programs that are build from source, and Debian does 
not do this.)

Cheers,

Mark.



      



-------------------- End of forwarded message --------------------

-- 
Ben Pfaff 
http://benpfaff.org



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to