dovecot - Nov 2004 - dovecot 1.0-test52 build notes

I thought I would try to use 'configure' to lay out the dovecot install
a little differently than the default.  I prefer all the support files
under one tree (e.g. in /usr/local/lib/dovecot-1.0) rather than
distributed around the filesystem.  And I'd be happiest if all of the
support files were just at that top level rather than in subdirectories.
e.g.:

   /usr/local/lib/dovecot-1.0/dovecot.conf
   /usr/local/lib/dovecot-1.0/imap-login
   /usr/local/lib/dovecot-1.0/dovecot-auth

etc.  (I'm happy to have a "doc" subdirectory though.)  And
ideally I'd
have the primary executable installed in a more generic place, but
tagged with its version number, like /usr/local/sbin/dovecot-1.0
Note that I'm not suggesting this, just explaining what I am after.

So the second to last thing I tried was:

   --program-suffix=-1.0 \
   --bindir=/usr/local/lib/dovecot-1.0 \
   --sbindir=/usr/local/lib/dovecot-1.0 \
   --libexecdir=/usr/local/lib/dovecot-1.0 \
   --sysconfdir=/usr/local/lib/dovecot-1.0 \
   --datadir=/usr/local/lib/dovecot-1.0 \
   --localstatedir=/usr/local/lib/dovecot-1.0 \

But that didn't really work, for the reasons listed in the "last"
try
below, plus all of the executables got the "-1.0" suffix, not just the
"dovecot" program (not a big surprise..).

And the last thing I tried:

   --bindir=/usr/local/lib/dovecot-1.0 \
   --sbindir=/usr/local/lib/dovecot-1.0 \
   --libexecdir=/usr/local/lib/dovecot-1.0 \
   --sysconfdir=/usr/local/lib/dovecot-1.0 \
   --datadir=/usr/local/lib/dovecot-1.0 \
   --localstatedir=/usr/local/lib/dovecot-1.0 \

which kinda got me where I wanted, except that if I want a dovecot-1.0
executable in /usr/local/sbin I need to add that by hand, and also that
the build process added another subdirectory "dovecot":

   /usr/local/lib/dovecot-1.0/dovecot/

I can (and did) manually remove that final directory and flatten out the
tree, and fortunately you've made it possible to specify in dovecot.conf
the paths to all the executables and so forth.  But it would be nice to
be able to create this desired layout entirely via configure and not
have to move things around after the fact.  Is that even possible?
Obviously, don't spend a lot of time on it.. but if I'm missing an
option that would get me where I want, I'd be interested in knowing
about it.

Oh, and "strings src/master/dovecot | grep /usr/local" gives this:

    /usr/local/lib/dovecot-1.0/dovecot.conf
    /usr/local/lib/dovecot/imap
    /usr/local/lib/dovecot-1.0/dovecot/imap
    /usr/local/lib/dovecot-1.0/run/dovecot
    /usr/local/lib/dovecot-1.0/dovecot/dovecot-auth
    /usr/local/lib/dovecot-1.0/dovecot/imap-login
    /usr/local/lib/dovecot-1.0/dovecot/pop3-login
    /usr/local/lib/dovecot-1.0/dovecot/pop3
    /usr/local/lib/dovecot/pop3

So it looks like there are a couple of places where the configured
paths aren't caught (or so it would seem).

Yours,
-mm-

On 6.11.2004, at 23:19, Mark E. Mallett wrote:
> which kinda got me where I wanted, except that if I want a dovecot-1.0
> executable in /usr/local/sbin I need to add that by hand, and also that
> the build process added another subdirectory "dovecot":
>
>    /usr/local/lib/dovecot-1.0/dovecot/
>
> I can (and did) manually remove that final directory and flatten out 
> the
> tree, and fortunately you've made it possible to specify in 
> dovecot.conf
> the paths to all the executables and so forth.  But it would be nice to
> be able to create this desired layout entirely via configure and not
> have to move things around after the fact.  Is that even possible?
> Obviously, don't spend a lot of time on it.. but if I'm missing an
> option that would get me where I want, I'd be interested in knowing
> about it.
Those configure options are mostly meant to specify locations to some 
root directories in some UNIX filesystem "standard". I don't think
it's
worth the trouble to make it possible to specify every single 
subdirectory that Dovecot uses now, or might use in future, to 
configure.

Your configure script parameters are long enough that you might as well 
build a script that moves the files exactly where you want :)
>     /usr/local/lib/dovecot/imap
>     /usr/local/lib/dovecot/pop3
>
> So it looks like there are a couple of places where the configured
> paths aren't caught (or so it would seem).
These are module directories. Use --with-moduledir too.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20041108/3d71e03c/attachment-0001.bin>

On Mon, Nov 08, 2004 at 04:19:16AM +0200, Timo Sirainen
wrote:
> On 6.11.2004, at 23:19, Mark E. Mallett wrote:
> 
> Your configure script parameters are long enough that you might as well 
> build a script that moves the files exactly where you want :)
Yep. 

> >    /usr/local/lib/dovecot/imap
> >    /usr/local/lib/dovecot/pop3
> >
> >So it looks like there are a couple of places where the configured
> >paths aren't caught (or so it would seem).
> 
> These are module directories. Use --with-moduledir too.
Indeed, that caught it.

-mm-