over the past days (and I may be off by a mile here), the current set
of Caudium/PExt modules (ab)use some or other pike aclocal.m4 macros
in an aclocal/automake context, somehow leading to the uncomfortable
situation with the debian packages' redistribution of those internals
to an overly exposed location.
Is that the case (leading to the small skirmish conflict of whether
the bug is in pike, or in those modules), or is there no particular
rational argument behind keeping "pike -x module" in its current
broken state (except for "I am not familiar with this, do not use it
myself and haven't had the time to look at it closely yet", as I
believe Marek has almost said) for the benefit of those modules?
(I've really been trying to understand Marek's point of view, despite
not being fully educated on automake and friends.)
/ Johan Sundström (Achtung Liebe!)
Previous text:
>2004-01-27 16:54:
>Subject: Re: Pike @ Debian
>--------------------------------------------------------------------
>The one and only way to compile Pike modules that should be endorsed
>and/or developed is "pike -x module". That's it. If it doesn't work
>it. If it requires the entirety of Pike, deal with it.
>
>That's about all I have to say.
>
> / David Hedbor
>