Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 06:31
    ferdnyc commented #8282
  • 06:04
    ferdnyc commented #8404
  • 05:57
    ferdnyc edited #8404
  • 05:56
    ferdnyc opened #8404
  • 05:02
    Astrum-polaris synchronize #8393
  • 04:22
    naveen521kk reopened #8271
  • 04:22
    naveen521kk closed #8271
  • 03:35
    naveen521kk commented #8397
  • 03:34
    naveen521kk ready_for_review #8397
  • 03:24
    jeremyd2019 commented #35
  • 02:52
    naveen521kk commented #8402
  • 02:51
    naveen521kk synchronize #8402
  • 01:10
    Schala edited #8403
  • 01:10
    Schala synchronize #8403
  • 00:54
    Schala opened #8403
  • Apr 17 21:53
    Astrum-polaris synchronize #8393
  • Apr 17 21:48

    github-actions[bot] on srcinfo-cache

    x264: pin commit (compare)

  • Apr 17 21:44

    lazka on master

    x264: pin commit (compare)

  • Apr 17 21:04
    jeremyd2019 commented #34
  • Apr 17 20:54
    Astrum-polaris synchronize #8393
David Macek
@elieux
For correct function, it requires other patched packages.
Biswapriyo Nath
@Biswa96

https://github.com/git-for-windows/MINGW-packages/tree/main/mingw-w64-git

Also that folder contains source code, do we want to store those here?

umarcor
@umarcor
@mingwandroid, WRT :point_up: January 10, 2021 11:27 PM no worries, I'm not in a rush to have it done, just slightly annoyed/frustrated because finding the workaround is being harder than packaging several other tools. Hope they let you out soon! (despite not having much outside to go to :S)

it should work if you create a branch or PR though

@Alexpux, @lazka I can confirm that branches/PRs are properly processed and several tools are built. If they depend on each other, the proper build order is picked and tools are installed before building the next.

That is true for forks of msys2/MINGW-packages too, even if a PR was not created yet.
jeremyd2019
@jeremyd2019
@lazka msys2 cmake failure from https://github.com/msys2/msys2-autobuild/runs/1693585949?check_suite_focus=true - issue with autobuild providing staged packages for dependencies?
2 replies
Maria Kerr
@mkmk0202_gitlab
Can someone help where we can find EULA or license of MSYS2?
Christopher Degawa
@1480c1
Msys2 probably doesn't have a collective license since it's more like a combination of programs and projects and patches
1 reply
Алексей
@Alexpux
@Biswa96 about evince, need to compare files in your package and in CI
Biswapriyo Nath
@Biswa96
How? I have diff pacman -Fl and pacman -Ql. Then compare ntldd outputs. No change.
Алексей
@Alexpux
what if open both packages in archive tool and see what files bigger
give me your package
Алексей
@Alexpux
@Biswa96 I check my local build
it also bigger
difference are in help files
CI create symlinks in package
my local build create copies
Biswapriyo Nath
@Biswa96
:relieved:
Christoph Reiter
@lazka
@jeremyd2019 yeah, somehow one of the dependencies (icu) is not getting pulled, I'll have a look later
Johannes Schindelin
@dscho

any thoughts on adding a mingw git by syncing in https://github.com/git-for-windows/MINGW-packages/tree/main/mingw-w64-git

yes @dscho ^

Git for Windows overrides the MSYS2 runtime because it needs a couple tweaks to pass Git's test suite. It's therefore not enough to just sync mingw-w64-git. I never managed to convince Alexey to work together on resolving those issues and gave up a couple years ago. Maybe I should restart that effort, but my pandemic-related time constraints make that a rather daunting idea right now.

Besides, Git for Windows' mingw-w64-git also adds the git-bash.exe and git-cmd.exe at the root directory, and /bin/bash.exe and /cmd/git.exe as convenience redirectors, which is probably not something MSYS2 would want to have. We'd need to figure out how to disentangle that (maybe as an extra package that has only those Git for Windows-specific global files) before we could move further on that.
David Macek
@elieux
Would you be okay with mingw-w64-git in MSYS2 not passing those tests?
Johannes Schindelin
@dscho
No.
A Git installation that fails the test suite is not a Git installation.
David Macek
@elieux
Does msys/git pass the suite?
Алексей
@Alexpux
are git-bash.exe is mingw program?
Johannes Schindelin
@dscho
I don't know, I'm not really interested in taking on responsibility for msys/git.

are git-bash.exe is mingw program?

Yes. They are in the root directory because otherwise users would not discover them in, say, a Portable Git.

David Macek
@elieux
My previous question wasn't meant to assume you would take responsibility over MSYS2's mingw-w64-git.
Does that make a difference?
Алексей
@Alexpux
well then we can create separate package for them using mingw-cross compiler
to not involve mingw subsystems
create msys package i mean
David Macek
@elieux
It doesn't make much sense even then. Git for Windows always is only mingw32 or only mingw64, so there can be one git-bash.exe outside. We can have both at the same time.
Алексей
@Alexpux
@elieux we must not install binaries from mingw package to msys root
David Macek
@elieux
I agree.
I'm just saying using mingw-w64-cross won't solve everything.
Алексей
@Alexpux
@elieux im just about providing git-bash.exe and git-cmd.exe
David Macek
@elieux
I know.
Should git-bash then open MINGW32, or MINGW64?
Алексей
@Alexpux
for what reason they created at all @dscho ?
David Macek
@elieux
They are in the root directory because otherwise users would not discover them in, say, a Portable Git.
It opens MinTTY with Bash with mingw-w64-git.
(Or conhost with cmd, in case of git-cmd.)
Алексей
@Alexpux
ok
Christoph Reiter
@lazka
@dscho thanks for the info
Johannes Schindelin
@dscho

for what reason they created at all @dscho ?

As I mentioned before: so that users discover them easier.

Biswapriyo Nath
@Biswa96
Are we allowed to copy ideas from Fedora?
Алексей
@Alexpux
what you mean
Biswapriyo Nath
@Biswa96
I mean like build command, flags, patches etc.