Re: Adding a new dict type

2010-11-23 Thread Victor Duchovni
On Tue, Nov 23, 2010 at 05:25:34PM -0500, Wietse Venema wrote: > > In that light, the headers don't get installed, and the API is still > > internal, but supports modular packaging. We would then compile all > > the supported table driver modules once we get past the initial > > dynamic linking hu

Re: Adding a new dict type

2010-11-23 Thread Wietse Venema
Victor Duchovni: > On Tue, Nov 23, 2010 at 03:12:02PM -0500, Wietse Venema wrote: > > > For compile-time libraries I think that the only practical option > > is not to make it configurable at all. Install them on the system > > library search path, such as > > > > /usr/local/lib

Re: Adding a new dict type

2010-11-23 Thread Victor Duchovni
On Tue, Nov 23, 2010 at 03:12:02PM -0500, Wietse Venema wrote: > For compile-time libraries I think that the only practical option > is not to make it configurable at all. Install them on the system > library search path, such as > > /usr/local/lib shared objects > /usr/local/inc

Re: Adding a new dict type

2010-11-23 Thread Victor Duchovni
On Tue, Nov 23, 2010 at 03:14:55PM -0500, Wietse Venema wrote: > Victor Duchovni: > > On Tue, Nov 23, 2010 at 01:43:35PM -0500, Wietse Venema wrote: > > > > > Victor Duchovni: > > > > Table drivers may depend on internal library interfaces that a > > > > particular > > > > application does not d

Re: Adding a new dict type

2010-11-23 Thread Wietse Venema
Victor Duchovni: > On Tue, Nov 23, 2010 at 01:43:35PM -0500, Wietse Venema wrote: > > > Victor Duchovni: > > > Table drivers may depend on internal library interfaces that a particular > > > application does not directly depend on, and so a statically linked > > > executable may not contain all th

Re: Adding a new dict type

2010-11-23 Thread Wietse Venema
Victor Duchovni: > On Tue, Nov 23, 2010 at 01:28:45PM -0500, Wietse Venema wrote: > > > Wietse Venema: > > > Victor Duchovni: > > > > There is a bit of pain around the ultimate location of the shared > > > > libraries > > > > Perhaps a simpler option is to link into each Postfix program just > >

Re: Adding a new dict type

2010-11-23 Thread Victor Duchovni
On Tue, Nov 23, 2010 at 01:43:35PM -0500, Wietse Venema wrote: > Victor Duchovni: > > Table drivers may depend on internal library interfaces that a particular > > application does not directly depend on, and so a statically linked > > executable may not contain all the pre-requisite entry-points.

Re: Adding a new dict type

2010-11-23 Thread Victor Duchovni
On Tue, Nov 23, 2010 at 01:28:45PM -0500, Wietse Venema wrote: > Wietse Venema: > > Victor Duchovni: > > > There is a bit of pain around the ultimate location of the shared > > > libraries > > Perhaps a simpler option is to link into each Postfix program just > enough bootstrap library code that

Re: Adding a new dict type

2010-11-23 Thread Wietse Venema
Victor Duchovni: > Table drivers may depend on internal library interfaces that a particular > application does not directly depend on, and so a statically linked > executable may not contain all the pre-requisite entry-points. The plug-in would not know how to call them anyway. Any comments on t

Re: Adding a new dict type

2010-11-23 Thread Victor Duchovni
On Tue, Nov 23, 2010 at 01:10:24PM -0500, Wietse Venema wrote: > Thus, the location of Postfix libraries needs to be frozen in at > build time, or else it needs to be patched into the executable at > installation time. Some programs require setgid privileges so we > can't rely in production usage

Re: Adding a new dict type

2010-11-23 Thread Wietse Venema
Wietse Venema: > Victor Duchovni: > > There is a bit of pain around the ultimate location of the shared > > libraries Perhaps a simpler option is to link into each Postfix program just enough bootstrap library code that it can read /etc/postfix/main.cf and then run-time link the shared Postfix lib

Re: Adding a new dict type

2010-11-23 Thread Wietse Venema
Victor Duchovni: > There is a bit of pain around the ultimate location of the shared > libraries No kidding. It breaks our current model, which allows the user to arbitrarily change all locations post-build (except config_directory, which is needed to find everything else). Thus, the location of

Re: Adding a new dict type

2010-11-23 Thread Victor Duchovni
On Tue, Nov 23, 2010 at 11:14:06AM -0500, Wietse Venema wrote: > > > In other words, we will still have to ship multiple Makfiles. > > > No, we can run "makedefs shared" to produce a shared-library build > > and "makedefs static" to product a static build. > > That was not clear from the patches.

Re: Adding a new dict type

2010-11-23 Thread Wietse Venema
Victor Duchovni: > On Tue, Nov 23, 2010 at 07:25:06AM -0500, Wietse Venema wrote: > > > Victor Duchovni: > > > On Mon, Nov 22, 2010 at 11:31:27PM -0500, Victor Duchovni wrote: > > > > > > > There is plenty of room for polish, but none of this rocket science, > > > > just some tedious wacking of t

Re: Adding a new dict type

2010-11-23 Thread Victor Duchovni
On Tue, Nov 23, 2010 at 07:25:06AM -0500, Wietse Venema wrote: > Victor Duchovni: > > On Mon, Nov 22, 2010 at 11:31:27PM -0500, Victor Duchovni wrote: > > > > > There is plenty of room for polish, but none of this rocket science, > > > just some tedious wacking of the library and program Makefile

Re: Adding a new dict type

2010-11-23 Thread Wietse Venema
Victor Duchovni: > On Mon, Nov 22, 2010 at 11:31:27PM -0500, Victor Duchovni wrote: > > > There is plenty of room for polish, but none of this rocket science, > > just some tedious wacking of the library and program Makefile after > > making some naming and style choices. I do not want to sound u