Hi, Today the last FreeBSD port about oxi version 0.14.0.1 has been committed. New versions will come soon.
Distributions from GH come without .git subdirectory, so I had to replace calls for vergen with the appropriate version number. Port/package system do not tolerate distributing sources in form of "git pull" or such. Only regular tarballs are welcome here. Also in case of client-html-mason I had to regenerate ill Manifest. Less official but more up-to-date site about ports: http://www.freshports.org/search.php?stype=name&method=match&query=openxpki&num=100&orderby=category&orderbyupdown=asc&search=Search More official but 1-2 days out-of-date site about ports: https://www.freebsd.org/cgi/ports.cgi?query=openxpki&stype=name&sektion=all Ports (source packages) are meant to run on all versions of FreeBSD and on some other *BSD systems -- without any change. We have to wait some time for new binary packages (for each supported architecture) to become available from the FreeBSD package building cluster. Binary packages for _old_ versions of oxi were _not_ available for FreeBSD-10, because they were incompatible with openssl-1.0 (which is the only choice on FreeBSD-10). You can get the latest version of all ports with portsnap fetch extract or update ports tree with portsnap fetch extract update After that you have a fresh tree of ports under /usr/ports, or wherever you configured it to be. E.g. /usr/ports/security/p5-openxpki /usr/ports/security/p5-openxpki-client-html-mason /usr/ports/security/p5-openxpki-i18n General introduction about use of officially distributed ports and packages is here: https://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ Comprehensive guide about porting/packaging is here: https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ I see no way around reading of the above two papers. A recommended tool for testing ports/packages as well as a very efficient binary package builder is: poudriere In some cases it is able to build binary packages meant for an architecture, which is different from that of the host. Say, if your host is amd64, you can build for amd64 _or_ for i386. [Just in case: nearly all new Intel processors fall into amd64 category.] This should be installed from ports/packages before use. E.g.: pkg install ports-mgmt/poudriere [A note for Linux addicts: after installing something, you have to run "rehash" to update list of executables on the path.] Poudriere's description is here: https://fossil.etoilebsd.net/poudriere/doc/trunk/doc/index.wiki Preparing of a new port could be a trivial or a very comprehensive task. As a rule, update of an existing port to a new version, is trivial. Long ago Julia and me tried to automate ports generation for oxi. You can still find that old and abandoned scripts in oxi sources under .../packages/freebsd/... But the output of these scripts still needed manual trimming. Take care: port standards have changed essentially since then. All the best, Sergei ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ OpenXPKI-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openxpki-devel
