On Thu, 2002-04-18 at 09:42, Dan Winship wrote:
> > Solution:
> > Though it took a lot of work to figure this out initially, I did get
> > this to work, and it does beautifully.  Thanks to [EMAIL PROTECTED] for
> > some help in debugging this.
> 
> That's '[EMAIL PROTECTED]'
Yes, I replied to myself with the correction.  Oops!

> 
> > The basic idea is to leave everything that
> > is managed by a package manger (ie in /usr) alone, and put all of our
> > needed libraries and applications for evolution CVS HEAD in /opt/gnome
> > (or similar).
> 
> I think it's less work overall to just not install gal-dev, gtkhtml-dev,
> or evolution from packages, and instead build evolution-1-0-branch in
> one prefix (say, /opt/evolution-1-0) and HEAD in another
> (/opt/evolution). That way you don't need to recompile all of gnome from
> the ground up. You only need gal, gtkhtml, and evolution in each tree,
> because both of them can use gtk, gnome-libs, etc, from /usr.
> 
I initially tried something like this, but it didn't work too well. 
evo-1-0 would not start and evo-head was really unusable (I did the
oaf-slay stuff).  I read in a gnome README somewhere that gnome doesn't
handle libraries being in different places too well, so I did it this
way.  Really though, I didn't want to touch evo-1-0 because it has
become such an integral part of my work.  Maybe I was TOO careful!  Like
I said at the top though-- if you like your current environment, don't
bother with this.

> > Do NOT run the evolution head (in /opt/gnome/bin) and the stable
> > evolution at the same time.  I also recommend not running them as the
> > same user since evolution head may (will?) break your stable evolution
> > configuration.  You must use the above export statements to run
> > evolution head as well.
> 
> There aren't currently any major config incompatibilities. I run them in
> separate prefixes as described above and use these .bashrc functions to
> switch between them:
> 
>     function evo10() {
>         oaf-slay
>         rm ~/evolution/config/storage-set-view-expanded*
>         export GNOME_PATH=/opt/evolution-1-0
>         export PATH=${PATH/evolution/evolution-1-0}
>     }
>     
>     function evohead() {
>         oaf-slay
>         export GNOME_PATH=/opt/evolution
>         export PATH=${PATH/evolution-1-0/evolution}
>     }
>     
> The oaf-slay is because you need oafd to be running with the correct
> PATH and GNOME_PATH. The 'rm' in the evo10 command is to fix a problem
> where otherwise the folder tree isn't visible when switching back to 1.0
> after using HEAD.
> 
> -- Dan

This is interesting.  I tried to run evo-head using my same
configuration (backing ~/evolution of course) and it brought me to the
evo setup screens.  Then when I restored from backup and used evo-1-0,
it did the same thing (setup again).  I assumed it changed something in
./.gnome somewhere, which I didn't backup.  It wasn't horribly bad-- my
mail, contacts and all were still there, I just had to reenter my mail
accounts and lost some preferences.  Should I have backed up more than
~/evolution?

Thanks for the feedback!

Jamie

-- 
Email:        [EMAIL PROTECTED]
GPG/PGP ID:   26384A3A
Fingerprint:  D9FF DF4A 2D46 A353 A289  E8F5 AA75 DCBE 2638 4A3A

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to