Re: upstreams that make mac app bundles - doctrine?

[Jonathan Schleifer <js%NetBSD.org@localhost>]

It's not just .app, it's bundles in general. E.g. should we build 
.frameworks?

IMO yes! See e.g. how devel/objfw handles it. There's the .dylib for 
compatibility with stuff that doesn't expect anything special, but there 
is also the .framework for things that want to be … more native.

Also keep in mind that in some cases, it's not possible to build 
something as an .app / .framework -- for the simple reason that those 
can contain extra files (resources, other binaries, etc.) that would be 
missing otherwise.

But yeah, I think if something is built as an .app, there at the very 
least should be a symlink in ${PREFIX}/bin. If there is one, there's 
very little reasons against an .app - it will behave just like on other 
systems because you can just execute e.g. "gimp", but you do get a 
proper icon in your dock etc. (and an .app is a hard requirement for that).

--
Jonathan