----- re: github SVN incompatibility to Cygwin
In fact it does connect, and also does transfer some SVN administration files (the stuff in ".svn" subfolders), but apparently the diff checking systems are incompatible which leads to no real payload being transferred. The overall effect is of course just as useless as if no connection at all was made.
Originally Posted by E P
Fortunately the slik SVN client that deba5er reminded me of can solve this problem for Cygwin users like myself.
I'll just need to check that this also works with the new versions of SlikSvn that have now been released.
----- re: Debugged version of PS2-Packer
Ok. I'll check out the sources and see what I can try in Cygwin/MinGW too, though that would make it dependent on their DLLs.
I had to compile my own from source with this change here
. I never could get it to compile in Windows and Pixel said that he used a cross compiler to build the Windows' binary of ps2-packer from Linux. I'll try to post more on that in a bit.
----- re: syncing our setups for both Linux and Cygwin
I know what you mean, and it's always a good idea to keep our options open.
No rush besides I've been meaning to get a partial Cygwin PS2 setup for my laptop and see what other issues may need workarounds.:) I would hate to throw away all that stuff that worked so well for so long.
Yes, and that would probably cause big trouble if we tried to graft an SVN client from a newer Cygwin package into one of the old Cygwin setups, which are required for compatibility with the old Gnu assembler methods needed by some of our libs. It's weird though that Linux setups somehow get around those problems, though newer Cygwin setups never can...
I wonder if we can find a standalone subversion executable slightly newer that we can just swap into Cygwin to get around this. It was sometime ago that I attempted to do just that but subversion requires a lot of libraries and they are tailored to the Cygwin package that they are built from.:(
----- re: github incompatibility issues
Yes, I know, and with the VMware setups made for that purpose it works just fine, since those use a recent Ubuntu version fully compatible to github.
Yeah, that figures. I wasn't a big fan of github anyway but I've seen quite a few of the regulars from over at ps2dev so it looks like github is where the future stuff will be placed for now. Even the newer versions of OPL are using it.
Effectively I think the dev scene as a whole has caved in, and allowed github to simply redefine the SVN usage.
That's clearly beyond our reach to affect either way, so we just have to adapt to it.
That sounds interesting, though the word 'portable' is not always used the same way by different people.
I've stayed away from the VMware myself because I figured I had something far superior. A portable Linux distribution that it too can run virtually anywhere and is itself a full blown system that can be configured to do just about anything and everything under the sun. Of course, it's taken me years to get it where I have it currently.
But I'd settle for either a DVD-based or USB-stick based setup which can be used to start a Linux system without in any way affecting the configuration of the OS normally used on that computer.
I don't think its advisable to 'swap' the binaries physically, as the svn.exe program file is just one of many binaries in the SlikSvn installation.
That slik svn
looks pretty slick. That could work as a drop in replacement for the included subversion that operates with Cygwin. Hopefully it's just a matter swapping out the Cygwin version for this one to workaround the github issue.:)
And I don't even know if those binaries are mutually dependent on each other, but I'd hate to find it out 'the hard way' (meaning messed up sources).
But I get fine results from just providing an alternate launch path in the script, so that is what I'm going to go for now.
You can read a bit more about it in my reply to deba5er, which I made before this post.
Best regards: dlanor