On 2018/03/28 11:12, Nils Gillmann wrote:
> Hello,
>
> I'm interested in providing our software (GNUnet) and its dependency chain
> through ports. As I like to work with Operating Systems and adjust my work
> to their expectations:
>
> - Do you prefer to build from ./bootstrap on (which sometimes might
> require autotools), or do you have any advice for me how OpenBSD likes
> to build packages?
> For example, you seem to build curl just as-is, but maybe there is
> a more conveniet bsd-prefered way I could integrate into gnurl?
I can't answer specific to GNUnet but can give some general ports
advice.
If you're using autoconf then it's preferable to ship generated
configure scripts in the tar release rather than have users generate
their own (with whichever version of autoconf they happen to have).
We do have a standard ports infrastructure method of running autoconf
(originally intended used when we have to patch autoconf input files)
or for verifying that the supplied configure script is not bogus, we
are finding we have to use this sometimes with software that doesn't
provide a generated script as well but that's not preferred.
> Node has an "BSDmakefile". So what I'm looking here for is advice
> or further reading material and opions from people working longer
> with ports for a newcomer to ports and building for OpenBSD.
Unless there's some special requirement it's usually best to have
only a single build infrastructure, not using e.g. autoconf on some
OS, BSDmakefile on others, etc. They always get out of sync.
> - Your gnutls package in ports states:
>
> # OpenBSD's unbound does not provide libdane
> CONFIGURE_ARGS += --disable-libdane
>
> Here the problem is that we will optionally (in other words: we
> recommend) require a gnutls build with DANE functionality.
The comment is wrong here, should be "OpenBSD's unbound does not
provide libunbound" (which it seems is required for gnutls libdane).
Unbound is in the base OS not in ports and libunbound is unlikely to
be enabled there. It _may_ be possible to have a separate libunbound
port but generally prefer to avoid things like that.
> From past conversations in our developer community I know that
> GNUnet is not fully functional on OpenBSD. I don't recall the
> full list of problems, but could I get advice and feedback here
> once I run into these problems?
>
> Thanks
>
No comments:
Post a Comment