Re: [PATCH] Windows: git-shell can be compiled again

Hi,



----- Original Message ----

From: Johannes Sixt <redacted>
In order of increasing difficulty:

- Run the tests on different platforms and servicepack levels.

I have no access to multiple boxes but when more people start using git locally, I will try that.
 

- Find a way to build perl scripts that is acceptable for upstream git.git
and that also works on MSYS/MinGW. Currently we still modify the build
procedure, and the results do not work during 'make test'.

Could you please elaborate on the above. Do you mean, rewrite some perl scripts or something else?
 

- Give some love to git-svn.perl. It will be removed from msysgit's
1.6.0.x release because it raises expectations that cannot be fulfilled.

Since I do not work on SVN, that would be tough in the present state for me. SVN does not even ship their perl bindings for perl 5.10 and I just could not build it from source. I was considering hacking 'svk' to bring back p4 support (which has been dropped in its current avatar).

Please dig the list archive: http://groups.google.com/group/msysgit

I will look into it.
 

I don't think a lot can be done performance-wise unless you want to help
port scripts to C.

No promises here as I do not know the complexity of perl scripts.

-dhruva



      Get an email ID as yourname@ymail.com or yourname@rocketmail.com. Click here http://in.promos.yahoo.com/address

dhruva schrieb:

quoted

From: Johannes Sixt <redacted>
- Find a way to build perl scripts that is acceptable for upstream git.git
and that also works on MSYS/MinGW. Currently we still modify the build
procedure, and the results do not work during 'make test'.

Could you please elaborate on the above. Do you mean, rewrite some perl scripts or something else?

No. I mean to have a better solution to the build procedure than commit
bd2f73a6ba6da in mingw.git. Look at that commit and at the 'use ...' line
that the build procedure inserts at the top of the perl scripts, and you
should understand the problem (hint: it's the colon in "C:/somwhere").

-- Hannes