In general, if any pike -x foo works in a standard "./configure && make && make install" installation of pike, but not in the debian/redhat/gentoo/whatever package, then it's a bug in the debian/redhat/gentoo/whatever packaging (which of course might also indicate a problem in pike itself).
Talking about pike -x, two feature requests:
There should be some way to get pike to list available "tools", and that way should be listed by either pike --help or pike -x (it seems pike --help doesn't mention -x at all. I'm using Pike v7.4 release 20 when testing this).
For example, instead of
$ pike -x Pike: -x specified without tool name.
I'd like to see
$ pike -x Pike: You must provide the name of a tool. Available tools:
module Build a standalone pike module. pv Image viewer bench Pike benchmark
It would be nice to have the testsuite exersize all supported tools, and have pike -x testsuite run the testsuite.
Then pike -x testsuite on an installed system is an easy way to test if the installation workd properly. Maintainers for various pike packaging could be encouraged to use pike -x testsuite to test their packages after installation.
Providing a testsuite is a precise way of saying that an appearantly obscure feature like pike -x module is actually both supported and expected to work.
/ Niels Möller (vässar rödpennan)
Previous text:
2004-01-26 21:51: Subject: Re: Pike @ Debian
On Mon, Jan 26, 2004 at 09:35:08PM +0100, Per Hedbor () @ Pike (-) developers forum scribbled:
Well, debian is way less flexible. And you seem to be intentionally
The difference is that it's pike one installs in Debian and not Debian in Pike.
minsunderstandning things in texts we write.
yep, as always. You should have gotten used to that.
Pike modules are internal to the pike build process.
How is that relevant to the discussion? Show me a single place where the pexts, php4 or caudium C Pike modules need the Pike interpreter to compile and link.
marek
/ Brevbäraren