On Thu, 2002-06-13 at 16:09, Junichi Uekawa wrote:
> Joseph Carter <knghtbrd@bluecherry.net> immo vero scripsit:
>
> > Okay, let's see if we can put this as simply as possible, for everyone
> > involved:
>
> I can provide simple steps in 2 lines:
>
> 1. get automake1.6 installed into Debian
> 2. Update build-depends of packages to automake1.6 (repeat 300 times)
>
> What is so crippling about that?
>
#2 also requires updating those packages to autoconf2.5, which in many
people's opinions is still unproven.
This could be a large change, and could involve having to rewrite a lot
of m4 macros if that package is a complex one. The next time a new
upstream version arrives that changes one, the maintainer's got even
more work mainting it.
It should be OK for packages to build-depend on automake1.4 and
autoconf2.13 (not that they'd need to, unless the package is missing
it's Makefile.am/configure.in files).
Remember: automake & autoconf should not be something that build
platforms need worry about - they're only for the maintainer who runs
them if he changes Makefile.am/configure.{in,ac} before generating the
diff. The source package shouldn't *need* them (if it does, I'd
consider that a bug).
Scott
--
Scott James Remnant Have you ever, ever felt like this? Had strange
http://netsplit.com/ things happen? Are you going round the twist?
Attachment:
signature.asc
Description: This is a digitally signed message part