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

[TD-135] Support illumos (non gnu-which) in PKI scripts #134

Closed
taskwarrior opened this issue Feb 12, 2018 · 5 comments
Closed

[TD-135] Support illumos (non gnu-which) in PKI scripts #134

taskwarrior opened this issue Feb 12, 2018 · 5 comments
Labels
bug Something isn't working won't fix
Milestone

Comments

@taskwarrior
Copy link

Thomas on 2017-08-27T10:51:56Z says:

The which command is different on all operating system from Linux to *BSD and illumos (SunOS). For that reason the following command result in an error:
{code:java}
CERTTOOL=$(which gnutls-certtool || which certtool){code}
Because which on illumos always output the lookup path at stdout.
{code:java}
$ CERTTOOL=$(which gnutls-certtool || which certtool)
$ echo ${CERTTOOL}
no gnutls-certtool in /usr/local/sbin /usr/local/bin /opt/local/sbin /opt/local/bin /usr/sbin /usr/bin /sbin /opt/local/bin/certtool{code}
 Affected shell scripts:

  • pki/generate.ca
  • pki/generate.client
  • pki/generate.crl
  • pki/generate.server

Recommendation:

 Replace which with type -p or create a full if-query with output redirection.

@taskwarrior taskwarrior added this to the Backlog milestone Feb 12, 2018
@taskwarrior taskwarrior added bug Something isn't working won't fix labels Feb 12, 2018
@taskwarrior
Copy link
Author

Migrated metadata:

Created: 2017-08-27T10:51:56Z
Modified: 2017-12-10T04:43:29Z

@taskwarrior
Copy link
Author

Paul Beckingham on 2017-10-12T02:43:08Z says:

Send a (portable) patch.

@taskwarrior
Copy link
Author

Thomas on 2017-10-13T11:17:35Z says:

I've attached attached a patch ( [^0001-Posix-compatibility-for-pki-shell-scripts.patch] ) which provide the most portable and POSIX compatibility. If you have any question feel free to contact me.

@taskwarrior
Copy link
Author

Paul Beckingham on 2017-12-10T04:43:29Z says:

This patch was generated against either the master or 1.1.0 branch (same thing) and is already released.  The development branch is 1.2.0, which already has this kind of portability fix on it.

@pbeckingham
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working won't fix
Projects
None yet
Development

No branches or pull requests

2 participants