Opened 14 years ago
Closed 11 years ago
#23157 closed enhancement (wontfix)
openssl install links
Reported by: | clemc@… | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.2 |
Keywords: | Cc: | ||
Port: | openssl |
Description
Not complaing -- this great stuff... but it would be nice if the install script automatically linked */bin/openssl and {dgst,md5,md4,md2,sha,sha1,mdc2,ripemd160) which are all legal entry points to the command. The man page should so the same thing of course...
Clem Cole
Change History (4)
comment:1 Changed 14 years ago by mf2k (Frank Schima)
Cc: | clemc@… removed |
---|---|
Component: | ports → base |
Type: | request → enhancement |
comment:2 Changed 14 years ago by jmroot (Joshua Root)
Component: | base → ports |
---|---|
Owner: | changed from macports-tickets@… to mww@… |
Port: | openssl added |
Summary: | openssl install → openssl install links |
comment:3 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
comment:4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
We could do this. In fact, symlinks for the manpages are already being installed. However, under the heading "Changes between 0.9.1c and 0.9.2b [22 Mar 1999]", the CHANGES file says this:
So it seems creating these symlinks would undermine the developers' intentions of deprecating this usage 11 years ago. Or perhaps I misread this, or they've changed their minds since then.
I'm also concerned that installing a symlink "md5" would override Mac OS X's md5 program in /sbin. While they appear to produce the same output in my limited testing, I'm not yet convinced they behave identically in all circumstances, which might break software that expects "md5" to be /sbin/md5 on Mac OS X.
Apple's version of openssl in Mac OS X doesn't have these symlinks (binaries or manpages)