|
From: LRN <lr...@gm...> - 2013-09-17 04:09:57
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17.09.2013 07:00, Renato Silva wrote: > On 2013/9/16 LRN wrote: >> On 16.09.2013 21:06, Eli Zaretskii wrote: >>> On Mon, 16 Sep 2013 17:39:41 +0400 LRN wrote: >>>> Eli Zaretskii wrote: >>>>> I'd love to have a native git on my disk, as it would free me >>>>> from the need to maintain 2 separate and carefully segregated >>>>> MSYS installations. >>>> Bad idea. Git is better when it uses a POSIX compatibility >>>> layer. Cygwin, MSYS1, MSYS2 - anything is better than native. >>> >>> Can you elaborate why? Given the fact that the git executables are >>> in fact MinGW (i.e. "native") programs, what does the compatibility >>> layer add that is important not to lose? >> 1) Nativeness is achieved by throwing heaps of patches on top of >> official git releases. And msysgit now has to maintain them. 2) >> Because of the msys->mingw transition at runtime, there are >> corner-cases where path mangling does the wrong thing. Msysgit devs >> solve this by using a special, patched msys-1.dll where mangling >> works a bit differently. >> >> Compiling git for MSYS1 is something a single developer is able to do >> in one day, and you only need to patch git to make it compatible with >> the decade-old MSYS1 development headers (for MSYS2 it's even simpler >> - no need to patch git, just fudge the buildsystem a bit). And no >> mangling problems. >> >> > If it's so better and easier, then why didn't they just compile git for > MSYS instead of as a native MinGW program? Ask them. - -- O< ascii ribbon - stop html email! - www.asciiribbon.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQEcBAEBAgAGBQJSN9YGAAoJEOs4Jb6SI2CwihUH/iKmz6Zb1dUoEMNiRihNeVv6 llidpo3DSUS17KlgEn7Mm1cQLMjcHBZ6gFvDM3/5SW7gIZ3UztT6V+Die2tuIaeB GTREmRYrf95D4uGcQzw636Y5L/UyvuUztgf0boUcSkZHJVMUjMCEJvlQ7q98Zwr9 szwWOKJP6+AX6MY4BgG9s9i8tdC9vdqcBMbxOokVaI8bOUkDAl3Q5Phlf4sl6ZuD DFz1+WyjWlRRh6pZ6AZj50csk/ueuMR+AVz2NWnGld5nBflggRbS1wkVXsO+GTYj Uvug2MNYBB1pDEXpb+U4MzqKoLDSxrltkgyjhaKEQMgqq8FOjKNqK5Fe7CGcL+U= =WoCY -----END PGP SIGNATURE----- |