On Dec 31, 2008, at 11:38 AM, demerphq wrote:
And many of the people building perl would not have the GNV bash
package, so
the equivalent logic will need to be added to configure.com.
Will that be hard? I am willing to support as much as I can.
Processing the .patch file in configure.com should not be a big deal.
We already process it the old way when it just had the Perforce change
number in it, so we just need to update that to do what
make_patchnum.sh does. Running git to generate lib/Config_git.pl is
not possible at this point since there is as yet no git on VMS, so
those parts of make_patchnum.sh cannot currently be translated.
Since there is also no generally available rsync on VMS, the only
practical way to stay current with blead is to generate your own
snapshot on a system that does have rsync and/or git. If we haven't
already done so, it would be nice to document the recommended
procedure for generating a snapshot. I assume it involves running
make_patchnum.sh followed but some incantation of git --archive.
________________________________________
Craig A. Berry
mailto:craigbe...@mac.com
"... getting out of a sonnet is much more
difficult than getting in."
Brad Leithauser
