You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have "swapped" the MSYS and MinGW directory trees via a profile.xml to match what we had for msysgit. However, it makes more sense for us to simplify things by aligning the directory layout again with upstream MSYS.
And how are $__mpflavor_prefix and friends from mgwport effected?
Or to rephrase my question: Can we write mgwport files which are before and after the switch valid?
Hmm, maybe we need to re-think this. In upstream MinGW / MSYS (installed to C:\MinGW), if you start C:\MinGW\msys\1.0\msys.bat, you get this:
$ cd /
$ pwd -W
C:/MinGW/msys/1.0
I.e., a cd / does not take you to the installation directory, but to the root of the MSYS directory. While this makes sense from an MSYS point of view, it makes it unnecessary hard to access files in C:\MinGW from the MSYS shell. So, what do you think, should we keep things as-is?
Activity
dscho commentedon Oct 15, 2014
👍
dscho commentedon Oct 15, 2014
It would be enough for that
profile.xmlto lose its<system-map>section, yes? I.e.would become
... and then we have to identify all the places that still expect the
msysGitlayout... ;-)sschuberth commentedon Oct 15, 2014
Exactly. Your last sentence names the hard part.
t-b commentedon Oct 15, 2014
Does that mean we have to tweak every mgwport file?
sschuberth commentedon Oct 15, 2014
Probably not tweak every file, but we must ensure for every file that it still builds, and if not, then tweak it.
t-b commentedon Oct 15, 2014
Just to understand the implications. In the curl mgwport file I would need to change
to
or?
And while we are at it, it might also make sense to use the generic commands like
doincludeinstead of the ones hardcoding the paths with insinto.sschuberth commentedon Oct 15, 2014
Correct.
t-b commentedon Oct 15, 2014
And how are
$__mpflavor_prefixand friends from mgwport effected?Or to rephrase my question: Can we write mgwport files which are before and after the switch valid?
sschuberth commentedon Oct 15, 2014
Probably yes, I don't know and would have to research.
dscho commentedon Oct 15, 2014
@sschuberth do you think we will have to switch all
#!/bin/shto#!/msys/1.0/bin/shwith this switch? If so, I think we should not switch.sschuberth commentedon Oct 15, 2014
No, I'm very sure we don't need to do that, as Shell scripts that come from upstream also don't have that.
sschuberth commentedon Oct 23, 2014
Hmm, maybe we need to re-think this. In upstream MinGW / MSYS (installed to
C:\MinGW), if you startC:\MinGW\msys\1.0\msys.bat, you get this:I.e., a
cd /does not take you to the installation directory, but to the root of the MSYS directory. While this makes sense from an MSYS point of view, it makes it unnecessary hard to access files inC:\MinGWfrom the MSYS shell. So, what do you think, should we keep things as-is?59 remaining items
Fix rare segfault in sparse-index (git-for-windows#690)
Fix rare segfault in sparse-index (#690)
builtin/gc: fix condition for whether to write commit graphs
odb: properly close sources before freeing them
builtin/gc: fix condition for whether to write commit graphs
odb: properly close sources before freeing them
Fix rare segfault in sparse-index (git-for-windows#690)
builtin/gc: fix condition for whether to write commit graphs
odb: properly close sources before freeing them
Fix rare segfault in sparse-index (#690)
reftable/table: fix NULL pointer access when seeking to bogus offsets
reftable/table: fix NULL pointer access when seeking to bogus offsets
reftable/block: fix OOB read with bogus block size
reftable/table: fix NULL pointer access when seeking to bogus offsets
builtin/history: unuse the commit buffer after use