On Mon, Sep 2, 2013 at 5:02 PM, Stephan Witt <st.w...@gmx.net> wrote:
> Am 02.09.2013 um 16:42 schrieb Jean-Marc Lasgouttes <lasgout...@lyx.org>: > > > 01/09/2013 20:06, Stephan Witt: > >>> What is the status on this work ? Do you still want to get it in beta > 2 ? > >> > >> Yes, please. I've answered already in the thread "Re: Lyx2.1.0beta2 > issues ?". > >> > >> Here is the latest patch attached again. > > > > I have some questions, probably because I did not follow the discussion > well enough. > > > > 1/ why have this code in configure.py, which complicates the situation? > I would put this in the LyX::queryUserLyXDir code. This does not mean that > the copy code should not be written in python, but it could by another > script. > > I never wrote python code before. So I started adding some code where it > fit my needs best. > And initially I tried to not touch the LyX C++ code at all. > > > 2/ I still do not understand why it is needed to have a comple-time > switch. The behaviour could just be > > * if the userdir exists, use it > > * if it does not, create one and offer to import configuration from an > existing userdir. > > I do not see what is so horrible about that, especially for people who > do not change their userdir. > > It was horrible for the developers who are afraid the user directory > contents gets copied if they run > LyX with their version suffix and are used to start with an empty user > directory. > > > To me this issue has nothing to do with platform or > --with-version-suffix, it is just a matter of offering to populate a > non-existing userdir. > > > This code apparently only works when version suffix is set to -2.0 and -1.6. In some sense, this is rather arbitrary and the use might have any suffix he wants. On Windows the user dir looks like: "LyX2.0". Vincent
