On Fri, 2010-10-15 at 19:23 +0200, André Schnabel wrote:
> Am 15.10.2010 17:21, schrieb Michael Meeks:
> > So - here is my suggestion ;-) hopefully it annoys everybody, and it is
> > two-fold.
..
> (no question on 1. - harden the code for migration)
> ...
> > 2. we continue to do automati
Michael Meeks wrote:
> Speaking of which - I notice that neither us, nor up-stream register
> the migrationoo3.uno.so - so the "migrate from 3.x" code is never
> executed :-) we only migrate from 2.x - any ideas why that is ?
> (Thorsten?). I will push a fix to enable that in scp2 over the we
Hi Micheal,
Just two simple answers:
Michael Meeks wrote (29-10-10 19:04)
Speaking of which - I notice that neither us, nor up-stream register
the migrationoo3.uno.so - so the "migrate from 3.x" code is never
executed :-) we only migrate from 2.x - any ideas why that is ?
When instal
Hi guys,
On Fri, 2010-10-15 at 19:23 +0200, André Schnabel wrote:
> (no question on 1. - harden the code for migration)
Speaking of which - I notice that neither us, nor up-stream register
the migrationoo3.uno.so - so the "migrate from 3.x" code is never
executed :-) we only migrate from
Hi Michael,
Michael Meeks wrote (15-10-10 17:21)
So - here is my suggestion ;-) hopefully it annoys everybody, and it is
two-fold.
1. we trawl for broken configuration settings in the code,
and work to harden the code against bad configurations so
it at l
Hi,
Am 15.10.2010 17:21, schrieb Michael Meeks:
So - here is my suggestion ;-) hopefully it annoys everybody, and it is
two-fold.
(no question on 1. - harden the code for migration)
...
2. we continue to do automatic config migration since this is
a commonly desir
Hi guys,
Soo - I'm trying to understand and summarize where we are, and the
basic problems so we can make a good decision; here are some of them
that I see:
A. Config migration is not 100% reliable, sometimes it gives you
a broken config; if you remove your config - but
André Schnabel wrote:
> > well, this is surely not an easy decision to make - but there's
> > definitely a way to have LibO use a clean user dir, if you need it:
> >
> > -env:UserInstallation=file:///path/to/config
>
> and this will prevent, that LibO will migrate any old userconfig
> when this
Hi,
>
> well, this is surely not an easy decision to make - but there's
> definitely a way to have LibO use a clean user dir, if you need it:
>
> -env:UserInstallation=file:///path/to/config
and this will prevent, that LibO will migrate any old userconfig
when this path is used the first tim
Mechtilde wrote:
> please don't take any user information from older version without any
> agreemaent of the user
>
> If you do so you haven't the possibilityy to start *office with a new
> user directory e.g in case you destroy something yourself.
>
> If you don't want a dialog then create a use
Hello
please don't take any user information from older version without any
agreemaent of the user
If you do so you haven't the possibilityy to start *office with a new
user directory e.g in case you destroy something yourself.
If you don't want a dialog then create a user directory with the def
Hi,
Am 14.10.2010 07:51, schrieb Mechtilde:
please don't take any user information from older version without any
agreemaent of the user
I second this.
If you do so you haven't the possibilityy to start *office with a new
user directory e.g in case you destroy something yourself.
Correct.
On Tue, 2010-10-12 at 15:07 +0100, Michael Meeks wrote:
> Would it be possible to add a non-modal / floating / dialog to
> prompt
> users to migrate / import their macros from an old version if it
> hasn't
> been previously imported, and we know that they have really been
> editing / changi
On Tue, 2010-10-12 at 03:33 -0600, Noel Power wrote:
> > - problem is, the OOo code we inherit here has several bugs.
Ah - fun :-)
> I was about to add an Openoffice3 supported version but I see your
> comments that you are removing 'Basic' anyway from the MigrationSteps,
> did I get tha
Noel Power wrote:
> > Mechtilde thankfully reported a problem with old OOo 2.x user
> > installations, which get migrated over to LibreOffice automatically
> > - problem is, the OOo code we inherit here has several bugs.
> Aha, coincidentally I was looking at something similar ( and found
> myself
Hi Thorsten
On Tue, 2010-10-12 at 03:40 +0200, Thorsten Behrens wrote:
> Hi,
>
> Mechtilde thankfully reported a problem with old OOo 2.x user
> installations, which get migrated over to LibreOffice automatically
> - problem is, the OOo code we inherit here has several bugs.
Aha, coincidentally I
Hi,
Mechtilde thankfully reported a problem with old OOo 2.x user
installations, which get migrated over to LibreOffice automatically
- problem is, the OOo code we inherit here has several bugs.
So we talked a bit on IRC tonight, and we somehow figured it would
be a good idea to keep migrating ba
17 matches
Mail list logo
