Scott wrote:
...
> >  Maybe you ran a build as root at one point?
> 
> Incidentally, running a build as root is _never_ a good idea, 
> and not required at all.

Don't you need to be root for an RPM build?

The EDE uses sudo for RPM makes.  It would be nice to remove if it isn't
required.

(Seeing "dist" makes me suspect a previous RPM build...)


> For development builds, the best thing to do is to define at 
> least these two environment variables before running 
> 'configure' or running the make
> (caveat: I don't use the EDE*, and can't comment on what it 
> does about these things):
> 
> SIPX_INSTALLDIR=<your install root directory> 
> SIPXPBXUSER=<your own username>

The EDE uses SIPXPBXUSER=`whoami` and --prefix=$FULL_INSTALL_PATH on the
configure command-line.  Does that effectively accomplish what you
recommend?


> I use a different install root directory for each branch or 
> sandbox that I'm working on, so I have several at any given 
> time, 

EDE does too.  Everything (including $CODE, $BUILD, $INSTALL) is
contained in your WORKING directory.  You can name WORKING whatever you
want, and have as many of them as you like.

OK, there is one exception...  The TFTP server and FTP users are
configured to access
.../WORKING/INSTALL/var/sipxdata/configserver/phone/profile/tftproot
through the /tftpboot softlink.  If you switch between WORKING
directories, then update the /tftpboot softlink if you want phone
profiles to work.  (I've put a helper script for this on my EDE to-do
list.)


> SIPX_BUILD_LABEL
> 
> to be a token that will id which branch/sandbox I was 
> building - it shows up in version stamps so that I can see in 
> traces and snapshots which build something came from.

Good idea.  (I've put something similar on my EDE to-do list.)


> The above will allow even 'make install' to work with little 
> change to your system.  The one exception, if I recall, is 
> that you have to change the group ownership and permission on 
> a couple of the apache installation directories so that you 
> can write to them yourself (a one time operation);

I've never noticed any problem.  What's the symptom?


Thanks Scott.


-Paul
[email protected]


_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to