Alexandre Ferrieux wrote:
On 1/30/07, Stephen Lee <[EMAIL PROTECTED]> wrote:
In order to run a newer version I would need to set up a suitable perl
environment...
And even this would be unnecessary if there were a nighlty .exe (of
course under svn control, so that going back to any specific revision
would be trivial for the rest of us non-Perl-literate :-)
Would you consider this option, dear vss2svn gods ?
It would, by the way, save my life too in this precise case !
I had not investigated a nightly build simply because it seemed that
there would not be much more development on this project. I will look
into trying to streamline that process.
In the meantime, the only thing that the .exe does is unpack a bunch of
files (including the ActiveState Perl interpreter, modules, etc.) into a
temp directory and run the interpreter from there. Here is more info on
how this is done:
http://aspn.activestate.com/ASPN/docs/PDK/6.0/PerlApp_overview.html
It is probably possible to prevent PerlApp from removing those temporary
files (or maybe it even leaves them in place by default until the next
run) so it should be possible to overlay them with the current version
in order to get everything working.
toby
_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user
