Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenCoarrays version bump & upstreaming of patches #25

Open
zbeekman opened this issue Oct 8, 2019 · 2 comments
Open

OpenCoarrays version bump & upstreaming of patches #25

zbeekman opened this issue Oct 8, 2019 · 2 comments

Comments

@zbeekman
Copy link

zbeekman commented Oct 8, 2019

Hi, OpenCoarrays maintainer here 馃憢

A few questions:

  1. Could you take a look at master or the latest release of OpenCoarrays and let me know if there are changes we should be making so that you don't have to apply patches?
  2. We're about to mint a new release and it would be great if a newer version of OpenCoarrays could be packaged with YACP. I am not a cygwin user, but for minor version bumps I'm happy to submit PRs, especially if we can get to a point where patching is no longer required.
  3. Why is ruby needed?
@fd00
Copy link
Owner

fd00 commented Oct 12, 2019

  1. YACP is experimental. I think my patch is still dirty therefore it isn't appliable to official source repository.
  2. Same as above.
  3. Because my utility script (https://github.com/fd00/xezat) detects ruby file in source tarball. (However the result is not appropriate...)

@zbeekman
Copy link
Author

Ok, great. It looks to me like the biggest patch is just to force dynamic linking only, and not package/distribute static libraries. Some other distros (Fedora) are doing this too, so my plan is to add an option like the one in your patch to force static or dynamic libs only. I'll see if I can port over other stuff too, then submit a rough-draft PR for the next version of OpenCoarrays.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants