Vince Coen wrote to James Digriz:
 
VC> Looking at the script SETUP.sh the obvious one is ths HOME setting but
VC> There are other instances of /opt being used and I suggest that a new 
VC> variable
VC> be setup say $HOMEROOT set as =/opt
VC> 
VC> With all the scripts vars using /opt changed to use HOMEROOT.
VC> 
VC> So now we have two vars near the beginning that need to be changed when 
VC> the
VC> --prefix param is used in configure somehow.
VC> 
VC> If that is done then the SETUP script will work.
VC> 
VC> Just a question of working out how :)
VC> 
VC> .. and now I do not know how configure work in order to try it.
VC> 
VC> Any one volunteering ?
VC> 
VC> 
VC> Vince
VC> 

Ok, it turns out there's not a whole lot to do. Configure doesn't touch
SETUP.sh or those scripts, and $HOME is already set in user mbse's profile, so
all that has to be done in SETUP.sh is to break $MHOME down:
MHOME_ROOT=/home (for example), or /opt, or  whatever you need. Then
MHOME=$MHOME_ROOT/mbse. 

You can then cd to the script directory and (again, for example):

sed s@/opt/@/home@/g rundoor.sh bbsdoor.sh

You can then  go back to the top-level source dir and do the same with 
SETUP.sh
at
 this point, but if you're compiling on *BSD you'll need then to readjust the
BSD
 references. I haven't done that since I'm not sure where Virtualmin puts its
user homes under BSD. I'll check into it when I get a chance. 

Now, change AC_DEFAULT_PREFIX=/opt/mbse to AC_DEFAULT_PREFIX=$HOME, run
autoconf, and you're good to go. Unless I've missed something, the only thing
left is to change any menu items needed. Configure or anything else doesn't
touch any
of those that I can see. That's something that might be addressed if/when the
code base is overhauled for new features or whatever. 

later,

                         
                                                         

    Greetings, James Digriz
    email: jbdigriz@bbs.dragonsweb.org

--- MBSE BBS v1.0.7.6 (GNU/Linux-x86_64)
 * Origin: DragonsWeb Labs  (1:123/755)