5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] courier-authlib a...
FromSent OnAttachments
Charles FryJul 14, 2006 8:28 am 
Martin OrrJul 14, 2006 8:38 am 
Charles FryJul 14, 2006 9:09 am 
AndrewJul 14, 2006 5:34 pm 
Sam VarshavchikJul 14, 2006 6:16 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] courier-authlib and /usr/libActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jul 14, 2006 6:16:01 pm
List:net.sourceforge.lists.courier-users

Andrew writes:

Martin Orr wrote:

On 14/07/06 16:29, Charles Fry wrote:

We are working on some issues with the Debian package of courier-authlib. The current package uses --prefix=/usr and so the shared libraries get installed in /usr/lib/courier-authlib. However section 10.2 of the Debian policy requires that shared libraries be installed in /usr/lib unless there is a compelling reason to do otherwise.

The Debian policy also says that libraries that are not meant to be linked to by third party executables should be installed in subdirectories of /usr/lib. Surely courier-authlib comes under this?

Okay, here's a really naive question. If the courier-authlib libraries aren't meant to be linked to by third-party executables, why document the api on the courier-authlib website?

So you can develop your OWN modules.