Thanks very much.
I almost certainly will have one more request, as I noticed that during the install of the port (pkg) it starts using paths of the staging directory. Though I might solve it with a patch in the package.
Further I will need to make a launch script that suits with the *BSD's...
I've updated the port - the URL / instructions remain equal.
So... it's now working! - as long you keep at least the "required options".
Still it ignores a number of configure options, like for example it insists in embedding it's own openssl, even if you ask for boringssl, or like installing...
Past 5 days I tried to make a FreeBSD port.
Seems it still has some obstacles before it's perfect (both the source as the port), but... I was getting somewhere.
If you wish to have a look:
portsnap fetch extract
these files need shebangfix for bash
these files need shebangfix, but I'm yet unable to patch that:
One more that could use the detect-download.sh
Plus in this file another shebang problem; if on FreeBSD there would be Bash, than /bin/bash wont be the path, but /usr/local/bin/bash
So "#! /usr/bin/env bash" would be more compatible.
--- src/modules/pagespeed/dlpsol.sh.orig 2019-01-05...
Another problem I with shebang's I see at ssl/util/echo.pl which starts with says /usr/bin/perl
while on probably most BSD that's /usr/local/bin/perl
All other .pl files have correctly
#! /usr/bin/env perl
Most of below is just cosmetics. But not all:
- In install.sh `source ./functions.sh bla` is a Bash thing. FreeBSD doesn't come with Bash, and if installed it comes with many dependencies. I think less software = less maintainance. The proper POSIX way should be `. ./functions.sh bla`.