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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add path independence #68

Closed
wants to merge 2 commits into from
Closed

Add path independence #68

wants to merge 2 commits into from

Conversation

minborg
Copy link
Contributor

@minborg minborg commented Aug 31, 2022

This small PR incorporated feedback from the original PR: #66 made after it was integrated.


Progress

  • Change must not contain extraneous whitespace
  • Change must be properly reviewed (no review required)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jextract.git pull/68/head:pull/68
$ git checkout pull/68

Update a local copy of the PR:
$ git checkout pull/68
$ git pull https://git.openjdk.org/jextract.git pull/68/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 68

View PR using the GUI difftool:
$ git pr show -t 68

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jextract/pull/68.diff

Webrev

Link to Webrev Comment

@minborg minborg mentioned this pull request Aug 31, 2022
2 tasks
@bridgekeeper
Copy link

bridgekeeper bot commented Aug 31, 2022

👋 Welcome back minborg! A progress list of the required criteria for merging this PR into panama will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Aug 31, 2022

@minborg This change now passes all automated pre-integration checks.

After integration, the commit message for the final commit will be:

Add path independence

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 11 new commits pushed to the panama branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@sundararajana) but any other Committer may sponsor as well.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added ready Pull request is ready to be integrated rfr Pull request is ready for review labels Aug 31, 2022
@mlbridge
Copy link

mlbridge bot commented Aug 31, 2022

Webrevs

Copy link
Member

@sundararajana sundararajana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we need similar change for many other samples. One flip side of the approach in this PR that we lose the specific version to use. C APIs need not be backward compatible (many are not!). Sample may work on a specific version of C library and not on the latest (or older) brew installed version.

@minborg
Copy link
Contributor Author

minborg commented Sep 1, 2022

Perhaps we could mention a specific version in the README file (e.g. the example here is verified for foo version x.y.z) and that appropriate changes might have to be made if another version is used.

@bondolo
Copy link

bondolo commented Sep 5, 2022

I guess we need similar change for many other samples. One flip side of the approach in this PR that we lose the specific version to use. C APIs need not be backward compatible (many are not!). Sample may work on a specific version of C library and not on the latest (or older) brew installed version.

As long as the library remains compatible the sample should continue to work. It seemed wrong to install a non-specific version using homebrew (or apt or yum) and then expect that specific version had been installed.

I agree with the suggestion that the readme should document which version of the library was used.

Copy link

@bondolo bondolo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

It is tempting to get fancy and implement everything needed to simultaneously support Linux and MacOS but the result would obscure the clarity of the sample so I agree to keep it simple.

(I am an OpenJDK Panama committer but have been inactive for 8+ years on the project so defer to more active contributors for approval).

@sundararajana
Copy link
Member

Note: "As long as the library remains compatible.." That is not true for all samples. For eg. libffmpeg has broken compatibility. Only specific older version works. May be the PR title should "Add path independence for libzstd sample".

@openjdk
Copy link

openjdk bot commented Feb 17, 2023

@minborg this pull request can not be integrated into panama due to one or more merge conflicts. To resolve these merge conflicts and update this pull request you can run the following commands in the local repository for your personal fork:

git checkout libstd2
git fetch https://git.openjdk.org/jextract panama
git merge FETCH_HEAD
# resolve conflicts and follow the instructions given by git merge
git commit -m "Merge panama"
git push

@openjdk openjdk bot added merge-conflict Pull request has merge conflict with target branch and removed ready Pull request is ready to be integrated labels Feb 17, 2023
@openjdk openjdk bot added ready Pull request is ready to be integrated and removed merge-conflict Pull request has merge conflict with target branch labels Feb 20, 2023
@bridgekeeper
Copy link

bridgekeeper bot commented Dec 4, 2023

@minborg This pull request has been inactive for more than 4 weeks and will be automatically closed if another 4 weeks passes without any activity. To avoid this, simply add a new comment to the pull request. Feel free to ask for assistance if you need help with progressing this pull request towards integration!

@bridgekeeper
Copy link

bridgekeeper bot commented Jan 2, 2024

@minborg This pull request has been inactive for more than 8 weeks and will now be automatically closed. If you would like to continue working on this pull request in the future, feel free to reopen it! This can be done using the /open pull request command.

@bridgekeeper bridgekeeper bot closed this Jan 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready Pull request is ready to be integrated rfr Pull request is ready for review
3 participants