Re: New port: devel/objfw

[Jonathan Schleifer]

This would be small enough if the package still built. Moving

SHARED_LIBS to 0.0 I get:

Error: /usr/obj/pobj/objfw-1.0/fake-amd64/usr/local/lib/libobjfw.so.0.0 does 
not exist
Error: /usr/obj/pobj/objfw-1.0/fake-amd64/usr/local/lib/libobjfwrt.so.0.0 does 
not exist
Error: /usr/obj/pobj/objfw-1.0/fake-amd64/usr/local/lib/libobjfwtls.so.0.0 does 
not exist

Ah, so the problem here was different definitions of soname. For me, the .0.0 is part of the soname, so it is indeed part of the soname after all (if going by my definition).

at make package time.  This is what Stuart meant when he said that the
port should be in control: SHARED_LIBS should decide the version used to
build and install the shared libraries.

So in plain English: OpenBSD wants to ignore upstream library version / soname versions and always use its own. Got it.

For automake or cmake ports this
is usually handled transparently by the ports infrastructure, which sets
various values in the build environment.  Here you don't seem to use
automake so you're probably going to need patches + ${SUBST_CMD} to inject
LIBobjfw_VERSION etc at the right spot.

Ah, perfect, this can just be overridden using MAKE_FLAGS. Done.

Regarding the port, I see two nits:
- Portable -> portable in COMMENT

Done

- maybe include your full name in MAINTAINER

Done

- .SILENT doesn't help understanding what is going on

The non-.SILENT output isn't too useful either, as that's just a bunch of shellscript then that loops over things.

and I wonder about two things:
- COMPILER + COMPILER_LANGS: is COMPILER_LANGS actually useful here?

You mean because Clang is guaranteed to support ObjC?

- is this framework already used by other applications in the wild?

I'm at least fairly certain not by anything else in OpenBSD ports ;).

   Could it be used as a building block for other ports?

Define building blocks. Like a Makefile template for other ports? I don't think so, it's just a regular library, users of the library can use whatever build system they want.

   Do we have to
   care about some existing ports automatically picking it up?

I don't think so, no.

That's a lot of questions, sorry :)

No worries, I hope I addressed everything with the new tarball I attached.

--
Jonathan

objfw.tar.gz
Description: application/gzip