Posted: Tue Jul 01, 2003 1:28 am Post subject: Neo replaces .sversionrc with its own
I think this was the case with Neo FY as well, but I note when you launch Neo IG, it replaces any existing .sversionrc file with its own. This is a bit of a pain.
Actually the OOo 1.0.3 GM installer also replaces any existing .sversionrc file with its own.
Both should be smart enough to append to an existing .sversionrc file. Fortunately "Start OpenOffice.org" supports multiple OOo versions in the .sversionrc file. In my case, I have now merged (using a text editor) the OOo 1.0.3GM and Neo IG .sversionrc files, putting the Neo IG version first. This allows me to launch either OOo 1.0.3GM or Neo IG without conflict.
I also note that Neo IG uses the pathname format rather than file:// URL format, and still refers to the version as 1.0.1 (which it probably is).
Joined: May 25, 2003 Posts: 4752 Location: Santa Barbara, CA
Posted: Thu Jul 03, 2003 9:39 am Post subject:
Yes, NeoIG and NeoFY and the OOo installer all happily go about replacing .sversionrc with their own. Even worse...NeoIG and NeoFY try to be clever and recreate the .sversionrc file if they sense they're being run as a new user or if the bundle was moved around on disk. Thus far the only consideration in NeoIG and NeoFY to coexisting with OOo is that they used different named pipes so they can launch side-by-side (previously, you could only have one or the other running!).
The reason why it's so fugly is that Neo was really the "dry run" of multiuser support and self-correcting installs. It tends to do boneheaded things that require you to go into .sversionrc and muck about manually to get both OOo and Neo installed and still uses the OO638C absolute path syntax. It was easier when both OOo and Neo were really "1.0.1" since their config directories could be shared, but no longer
NeoJ, however, has got the code that gets all of the config stuff right and improves on both OOo and NeoFY/IG. It uses a completely different name for the sversionrc file, differnet directories, and the like. Its multi-user support is solid as well, and Patrick also figured out the patch to get the "work" directory pointing to the right local location.
Eventually NeoJ will serve as the preferred way for launching Neo as well, that is, leaving .sversionrc for OpenOffice.org and using a separate set of files for Neo to avoid messing up folks' machines while playing with experimental software (not that people do that kidn of thing... )
But right now...beware if you want to get OOo running side-by-side with NeoFY and NeoIG, or get NeoFY and NeoIG running side-by-side...you'll have to ping here for help if you're not a .sversionrc expert
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum