On Tue, Nov 12, 2013 at 09:31:00AM -0600, Bruce Dubbs wrote: > Igor Živković wrote: > > On 11/12/2013 07:04 AM, Bruce Dubbs wrote: > >> Ken Moffat wrote: > >>> > >>> We could use --libexecdir=/usr/lib/dovecot, but that puts the > >>> libexec files file in /usr/lib/dovecot/dovecot/ or we could follow > >>> CBLFS and use --libexecdir=/usr/lib/dovecot/exec which puts them into > >>> /usr/lib/dovecot/exec/dovecot/ : preferences ? Personally, I would > >>> prefer to just let it use /usr/libexec, but I guess that is probably > >>> still too much in the redhat/gnu tradition for you guys. > >>> > >>> I'll fix it up later if we can agree about where to use, I've also > >>> got one other recent package that needs tweaking. > >> > >> I really don't have a problem with /usr/libexec. > > > > I'd prefer /usr/lib/dovecot/exec for consistency sake and to avoid > > double dovecot subdirectoy. > > I think I like that too. It's better than /usr/libexec/dovecot. > An ex-editor has pointed out to me that Arch use --with-moduledir=/usr/lib/dovecot/modules : I haven't tested this yet, but if upstream calls them modules then I guess that is the right name.
ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
