Toni Mueller wrote:
I'm underway mangling that into a similar structure as eg. have the
Python or PHP ports:
mail/courier
/authlib
/imap
/sqwebmail
That's a tossup for me, although there's the argument that
courier-authlib should go under security instead of mail, since it's not
really a mail program. We also want to avoid confusion between
courier-imap and courier-mta, since there's no reason to build the whole
courier-mta if all you want is the imap/pop3 part.
(would do for me, and have a unified structure for the whole beast, but
you probably also want)
/mta
/pop3
/... ?
They're subpackages, so they really don't need their own directory.
The uid mentioned above must exist at build time (ie, on both the build
system _and_ the target system), but I'm unsure about how to express
that - unless there'd be a fake package that contains only adding this
uid and gid, but do nothing else, and mention that as BUILD_DEPENDS and
RUN_DEPENDS.
I haven't tried patching configure_in and rebuilding configure, but
building courier-authlib works fine if you give it a numeric uid and the
user doesn't exist yet. You don't have to worry about the user existing
when you build/install courier-mta, since courier-authlib is a
dependency and will create the user if needed.
