At 11:23 23.11.2002 +1100, Tim Potter wrote:
On Fri, Nov 22, 2002 at 01:21:21PM +0100, Jelmer Vernooij wrote:--libexecdir=DIR program executables in DIR [EPREFIX/libexec]
> > here's a patch that added the 'modules path' parameter.
> >
> > lp_modules_path() is prefixed to all lp_modules() witch are not start with
> > '/' (not absolute pathes)
> >
> > the default for lp_modules_path() is selectable by ./configure
> > --with-modulesdir=/modules
> > or $(LIBDIR)/samba (when --with-fhs) or $(LIBDIR)
> >
> > make installmodules install the modules to lp_modules_path()
> >
> > make modules now makes proto_exist
> Thanks a lot! These were on my todo list.I'll take a look at it later today
> (when I get back home, I'm currently at school)
There's already a directory for architecture specific library files -
libexec. We haven't needed to use this so much before so it probably
isn't supported in configure.in. How about $(LIBEXECDIR)/modules as
a location for the vfs modules?
--libdir=DIR object code libraries in DIR [EPREFIX/lib]
I think modules are object code libaries
I would preferr to use LIBDIR/samba , LIBDIR/samba/modules , LIBEXECDIR/samba or LIBEXEC/samba/modules (but I would like one of the first two)
I also don't like the valid.dat , upcase.dat, lowcase.dat installed to LIBDIR they should go to LIBDIR/samba/ or CONFIGDIR/ (we should always use the subdir samba, exept BINDIR and SBINDIR)
because of that I want to change lib_path() to libsamba_path() and dyn_LIDDIR to dyn_LIBSAMBADIR.
Tim.
metze ----------------------------------------------------------------------------- Stefan "metze" Metzmacher <[EMAIL PROTECTED]>
