------=_Part_36478_19895472.1206809750431
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
I've been having a play with runbuild.sh and trying to get it to work on
Ubuntu (which I'll be raising a ticket for shortly)
I think runbuild.sh is great - you can basically now download the source
and
run one script to build ingres without any setting of environments
variables
etc. However I have a question about what it's intended for.
I hit a scenario this morning where I used runbuild.sh to build ingres,
then
needed to do a jam clean and rebuild. In order to do jam clean sucessfully
I
had to source source_me.sh to set up whatever it is that jam was looking
for
(it complained about "unknown rules"). However if I then re-run
runbuild.**** complains that ING_ROOT is already set.
So I was wondering whether runbuild.sh was intended to be used this way,
or
simply as a quick-start first build method? Useful for someone who wants
to
build ingres to use it but isn't going to do a lot of development?
ISTM that it would quite often be the case that you make some changes
which
would require having your environment set, and then want to re-build. In
this scenario if you use runbuild.sh you either need to log out and in or
have a separate window where you haven't set the environment (a separate
window is useful anyway so you can tail the log).
Not really a criticism, just wondering about how it's meant to be used.
Anyone else used it much yet?
--
Paul Mason
------=_Part_36478_19895472.1206809750431
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
I've been having a play with runbuild.sh and trying to get it to work
on Ubuntu (which I'll be raising a ticket for shortly)<br><br>I think
runbuild.sh is great - you can basically now download the source and run
one script to build ingres without any setting of environments variables
etc. However I have a question about what it's intended for.<br>
<br>I hit a scenario this morning where I used runbuild.sh to build
ingres, then needed to do a jam clean and rebuild. In order to do jam
clean sucessfully I had to source source_me.sh to set up whatever it is
that jam was looking for (it complained about "unknown rules").
However if I then re-run runbuild.sh it complains that ING_ROOT is already
set.<br>
<br>So I was wondering whether runbuild.sh was intended to be used this
way, or simply as a quick-start first build method? Useful for someone who
wants to build ingres to use it but isn't going to do a lot of
development?<br>
<br>ISTM that it would quite often be the case that you make some changes
which would require having your environment set, and then want to
re-build. In this scenario if you use runbuild.sh you either need to log
out and in or have a separate window where you haven't set the
environment (a separate window is useful anyway so you can tail the
log).<br clear="all">
<br>Not really a criticism, just wondering about how it's meant to be
used. <br><br>Anyone else used it much yet?<br><br>-- <br>Paul Mason
------=_Part_36478_19895472.1206809750431--
|
