Bug 103937

	

This is PR 1 of 8. Others to be submitted later this day.

If you consider 8 PRs (and possibly commit them) one by one 
in the order as labeled, then correct inter-dependencies of new ports 
will be preserved at all stages of this proposed update.

Suggesting update with a simultaneous split of existing port 
security/p5-openxpki into 8 new ports, 
which are annotated in respective pkg-descr files:

security/p5-openxpki (new ver is given in this PR 1 of 8)
security/p5-openxpki-client (PR 2 of 8)
security/p5-openxpki-client-cli (PR 3 of 8)
security/p5-openxpki-client-html-mason (PR 4 of 8)
security/p5-openxpki-client-scep (PR 5 of 8)
security/p5-openxpki-client-soap-lite (PR 6 of 8)
security/p5-openxpki-i18n (PR 7 of 8)
security/p5-openxpki-deployment (PR 8 of 8)

Reasons: 

Existing port embrased 8 essentially non-uniform distribution 
tarballs. This required eclectic and lengthy hand-work in Makefile, 
and ignoring many of automatic porting tools provided by the 
FreeBSD ports collection. Which in turn lead to non-reliabe and 
non-robust port with respect to changes of generall FreeBSD 
port-supporting tools. Also, the procedure of creating a common pkg-plist was
very complicated. It was a consequence of non-trivial 
interdependencies of distribution tarballs. This fact was in a background
of several problems with this port, including once labeling it as broken
due to the ill pkg-plist.

Each of the new ports proposed here use automatic tools of the 
FreeBSD port collection to the maximum possible extent, are much 
simpler to comprehend and support.

Also, user need not necessarily install all of 8 to work with the 
OpenXPKI collection. He/she should have a choice of tools to pick up.

And yes, I am with the developers team of the OpenXPKI project, and 
using this software every day.