The RESTEASY_LIB variable is currently defined in /etc/pki/pki.conf:
# RESTEasy library RESTEASY_LIB=/usr/share/java/resteasy
The variable should be moved into /usr/share/pki/etc/pki.conf where all other defaults are defined (e.g. JNI_JAR_DIR, future TLS settings), and customized at build time based on the target platform.
The /etc/pki/pki.conf should be left empty with just a comment similar to this:
# User-defined overrides go here. # Defaults are in /usr/share/pki/etc/pki.conf.
Applications should read both pki.conf as shell script as follows: 1. source /usr/share/pki/etc/pki.conf 2. source /etc/pki/pki.conf (overriding variables defined earlier) 3. read the variable
In Python the variable can be read as follows:
value = subprocess.check_output( '. /usr/share/pki/etc/pki.conf && . /etc/pki/pki.conf && echo $RESTEASY_LIB', shell=True) resteasy_lib = str(value).strip()
An upgrade script is needed to remove the variable from existing /etc/pki/pki.conf.
Proposed milestone: 10.3
Per CS/DS Meeting of 11/24/2014 - 10.3
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
Fixed in master branch:
Metadata Update from @edewata: - Custom field feature adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: fixed - Issue set to the milestone: 10.6.0 (was: UNTRIAGED) - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1771
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.