Zvi "Viz" Effron writes:

3c) authdaemond: I could not find a man page for authdaemond anywhere, and I
suspect this is one binary that may not need documentation, as it doesn't
seem like it's designed for users to run it.

3d) courierauthconfig: It appears that the man file for authlib documents
courierauthconfig.  I've added a line to my spec file to install the authlib
man page for courierauthconfig as well, but I think it would be better to
update the Makefile to install it along with the rest of the installed man
pages.  (However, that could be bad manpage practice, and I just don't know
it, in which case, please just let me know.)

courierauthconfig is also not something that's an "end user" needs. It's for use by configure scripts that build against courier-authlib. It probably needs to be documented somewhere, but not in a manpage.

3e) userdb-test-cram-md5: I also couldn't find a man page for
userdb-test-cram-md5, but it looks to me like a tool designed to help
sysadmins test their cram-md5 setup.  If that's the case, I think it would
be highly beneficial to create a man page for userdb-test-cram-md5
documenting its purpose and usage, especially since it does not respond to
--help, -h, or print a usage message when given no arguments.

It's just a Perl script, with some brief docs in its comments.

If any of the above should not have a man page, please let me know so I can
make sure to not include one in my rpm.

4) The reviewer for previous attempts to package courier-authlib for Fedora
(see the above link to Fedora's bugzilla) questioned why the core
courier-authlib libraries (libcourierauth*) were not installed to the
library directory but instead to the courier-authlib subdirectory.  I tried
to make the packages install to the base library directory, but when
compiled without the -rpath flag, libtool refused to install them
(complaining that they must be installed to a directory ending with
/usr/lib(64)/courier-authlib.  When I removed the -rpath flag from the
Makefile for the core courier-authlib libraries (again, libcourierauth*), I
received link errors on the various authentication modules.

There's ton of stuff that already gets installed to /usr/lib(64)/<subdirectory>. Just look in there. There's nothing unusual about installing to a subdirectory, when a package has several libraries.

At that point, rather than keep muddling around, I decided it was much
easier to just create an ld.so.conf.d entry for courier-authlib.  However, I
do still wonder, is there a reason for not putting the core libraries into
the base library directory?

It is not necessary to have an ld.so.conf.d entry for courier-authlib. The package works fine without it. The libraries that go in there get manually dlopened.

Attachment: pgpU560hsViFZ.pgp
Description: PGP signature

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to