force install instead of rebuild

[Hamish]

On Wednesday 02 November 2005 18:44, lucy at tettekop.com wrote:
> What do u mean use @forcere ?
> Add that somewhere in the conf file ?
> Where exactly ?
>
> Thanks.
>
> ----- Original Message -----
> From: "Hamish" <lists at subvs.co.uk>
> To: <kolab-users at kolab.org>
> Sent: Wednesday, November 02, 2005 7:16 PM
> Subject: Re: force install instead of rebuild
>
> > _______________________________________________
> > Kolab-users mailing list
> > Kolab-users at kolab.org
> > https://kolab.org/mailman/listinfo/kolab-users

Hi Lucy
If you check in obmtool.conf, it has instructions for obmtool to build your 
openpkg environment. Usually, running sh ./obmtool kolab will install the 
kolab openpkg environment, it will check if a package is installed, and skip 
if it is. If you want for example to add different config flags to packages, 
you can do so, and then change the @install to @forcere, ie:
@install ${altloc}apache-1.3.33-2.4.1_kolab (configure flags follow) would do 
nothing on an already-installed kolab, but if you wanted to use horde, you 
need to change a few parameters in the apache build, so you could get it to 
re-install with your new paramaters by changing the line to:
@forcere ${altloc}apache-1.3.33-2.4.1_kolab
and running sh ./obmtool kolab again.
If you want to completely start again, just delete everything in /kolab and 
run sh ./obmtool kolab again (from the directory where you downloaded the 
sources)
Hope that helps,
H
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.kolab.org/pipermail/users/attachments/20051103/5abe79ac/attachment.sig>