Gavin Smith wrote:
Also, if the *.c
file was missing from the release and the user didn't have xsubpp, they would
have no way to reproduce it, whereas if the *.c is incompatible and they
do have xsubpp, they could always delete the *.c file and then regenerate
it.

The Perl kit includes xsubpp -- if the user does not have xsubpp, they do not have an XS-capable perl and the *.c files are useless to them anyway. If they *do* have an XS-capable perl, xsubpp was installed along with it, barring *extreme* distribution packaging stupidity. Upstream GNU packages should not cater for that level of bad packaging.

Maybe we could reconsider it after the next release but I only want to make
very minor changes at this point.

That is fine if we are past a release code freeze, as long as this does get fixed in a future release.



-- Jacob

Reply via email to