Re: Bug#247176: Preparing a autobuildable package of perl for testing-proposed-updates
On 2004-08-09 Brendan O'Dea <firstname.lastname@example.org> wrote:
> On Thu, Aug 05, 2004 at 01:19:24PM +0200, Andreas Metzler wrote:
>> I am curently preparing an autobuildable package of perl for sarge.
>> The current version (5.8.4-2) required handholding and local patching
>> on ia64, arm and m68k which would make a security update a nightmare.
> While I'm not totally opposed to this patch, I'd be more inclined to use
> -Dcc=gcc-2.95 and post-edit it out of Config.pm.
I've explained on 2004-08-10 why the ugly solution should be chosen,
mainly because it is *tested* and because other files are contaminated
with cc=gcc-2.95, too.
> Calling the patch 63_debian_optim_workaround is more in line with the
> current naming convention (this is pretty debian-specific).
I've renamed the patch.
All this has happened almost three weeks ago without further comment
yet by Brendan, therefore I have decided to go for the NMU, time is
starting to become a pressing issue for sarge.
Dear release-managers: Are you interested in a autobuildable
perl-package for sarge? Do you want me to upload to tpu? The interdiff
is quite small (see URL) and the package builds successfully on i386
and ia64 (ia64 is one of the broken architectures.)
If I get a go I am confident to get a m68k build from Adam
Conrad before I upload the package.
 He announced to be offline for 10 days, that is why I waited that
"See, I told you they'd listen to Reason," [SPOILER] Svfurlr fnlf,
fuhggvat qbja gur juveyvat tha.
Neal Stephenson in "Snow Crash"