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

JDK-8275923: Override the LPR path using a system property #6052

Closed
wants to merge 1 commit into from

Conversation

rhbvkleef
Copy link

@rhbvkleef rhbvkleef commented Oct 20, 2021

On some select systems, the LPR binary may be placed elsewhere (for example at /app/bin/lpr). For that reason, we need to be able to override this value. This proposal also allows overriding the LP's path, as it could experience similar difficulties.


Progress

  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue
  • Change must be properly reviewed
  • Change requires a CSR request to be approved

Integration blocker

 ⚠️ Title mismatch between PR and JBS for issue JDK-8275923

Issue

  • JDK-8275923: Allow overriding the path to the lpr binary ⚠️ Title mismatch between PR and JBS.

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/6052/head:pull/6052
$ git checkout pull/6052

Update a local copy of the PR:
$ git checkout pull/6052
$ git pull https://git.openjdk.java.net/jdk pull/6052/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 6052

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/6052.diff

On some select systems, the LPR binary may be placed elsewhere (for example at `/app/bin/lpr`). For that reason, we need to be able to override this value. This proposal also allows overriding the LP's path, as it could experience similar difficulties.
@bridgekeeper bridgekeeper bot added the oca Needs verification of OCA signatory status label Oct 20, 2021
@bridgekeeper
Copy link

bridgekeeper bot commented Oct 20, 2021

Hi @rhbvkleef, welcome to this OpenJDK project and thanks for contributing!

We do not recognize you as Contributor and need to ensure you have signed the Oracle Contributor Agreement (OCA). If you have not signed the OCA, please follow the instructions. Please fill in your GitHub username in the "Username" field of the application. Once you have signed the OCA, please let us know by writing /signed in a comment in this pull request.

If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please use "Add GitHub user rhbvkleef" as summary for the issue.

If you are contributing this work on behalf of your employer and your employer has signed the OCA, please let us know by writing /covered in a comment in this pull request.

@openjdk
Copy link

openjdk bot commented Oct 20, 2021

@rhbvkleef The following label will be automatically applied to this pull request:

  • client

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the client client-libs-dev@openjdk.org label Oct 20, 2021
@rhbvkleef
Copy link
Author

/signed

@bridgekeeper bridgekeeper bot added the oca-verify Needs verification of OCA signatory status label Oct 20, 2021
@bridgekeeper
Copy link

bridgekeeper bot commented Oct 20, 2021

Thank you! Please allow for up to two weeks to process your OCA, although it is usually done within one to two business days. Also, please note that pull requests that are pending an OCA check will not usually be evaluated, so your patience is appreciated!

@bridgekeeper bridgekeeper bot removed oca Needs verification of OCA signatory status oca-verify Needs verification of OCA signatory status labels Oct 21, 2021
@magicus
Copy link
Member

magicus commented Oct 21, 2021

Hi @rhbvkleef,

This PR is not going to be noticed by anyone who can review it. Please send an email to the relevant mailing lists (in this case client-dev@openjdk.java.net) to raise a discussion and, hopefully, have someone sponsor this PR.

@rhbvkleef
Copy link
Author

@magicus

in this case client-dev@openjdk.java.net

That mailing list doesn't exist.

@magicus
Copy link
Member

magicus commented Oct 25, 2021

Sorry it's client-libs-dev@openjdk.java.net.

@rhbvkleef rhbvkleef changed the title Override the LPR path using a system property JDK-8275923: Override the LPR path using a system property Oct 26, 2021
@openjdk openjdk bot added the rfr Pull request is ready for review label Oct 26, 2021
@mlbridge
Copy link

mlbridge bot commented Oct 26, 2021

Webrevs

@prrace
Copy link
Contributor

prrace commented Oct 26, 2021

/csr

@openjdk openjdk bot added the csr Pull request needs approved CSR before integration label Oct 26, 2021
@openjdk
Copy link

openjdk bot commented Oct 26, 2021

@prrace has indicated that a compatibility and specification (CSR) request is needed for this pull request.
@rhbvkleef please create a CSR request for issue JDK-8275923. This pull request cannot be integrated until the CSR request is approved.

@prrace
Copy link
Contributor

prrace commented Oct 26, 2021

This needs a CSR since it introduces a new interface.
I also think we should consider if the hard coded path were always tried first and only if it doesn't exist would
we try the property ..
then we'd name the property appropriately, eg
-Dsun.print.lprFallbackCommand=/app/foo/lpr
"Command" not "Path".

I will also check with the team that assesses secure coding etc to ask what they think.

@bridgekeeper
Copy link

bridgekeeper bot commented Nov 23, 2021

@rhbvkleef 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!

@prrace
Copy link
Contributor

prrace commented Dec 17, 2021

Updates more or less along the lines above might make this acceptable

  1. The hardcoded location is tried first REGARDLESS of whether the property is set
  2. The property is only read ONCE - in something like a static initializer for the class or some mechanism that has the same effect.
  3. The property name is as described above.

@bridgekeeper
Copy link

bridgekeeper bot commented Jan 15, 2022

@rhbvkleef 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 Feb 12, 2022

@rhbvkleef 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.

@nanonyme
Copy link

nanonyme commented Oct 11, 2023

Hi @nanonyme, thanks for making a comment in an OpenJDK project!

All comments and discussions in the OpenJDK Community must be made available under the OpenJDK Terms of Use. If you already are an OpenJDK Author, Committer or Reviewer, please click here to open a new issue so that we can record that fact. Please Use "Add GitHub user nanonyme for the summary.

If you are not an OpenJDK Author, Committer or Reviewer, simply check the box below to accept the OpenJDK Terms of Use for your comments.

Your comment will be automatically restored once you have accepted the OpenJDK Terms of Use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client client-libs-dev@openjdk.org csr Pull request needs approved CSR before integration rfr Pull request is ready for review
4 participants