Bug#816173: [Pkg-lyx-devel] Bug#816173: Bug#816173: lyx: Lyx failed to start if the $HOME/.lyx does not exist
On Tue, 1 Mar 2016 10:40:49 +0100 Sven Hoexter wrote: > If not abort with an error message pointing > to the -userdir option. I think using the -userdir option is also the > way to go if you use lyx during build time in minimal build environments > like sbuild chroots. Agreed. I added hint for -userdir option in the error message. This will be fixed with lyx 2.4. Pavel
Bug#816173: [Pkg-lyx-devel] Bug#816173: Bug#816173: lyx: Lyx failed to start if the $HOME/.lyx does not exist
On Mon, Feb 29, 2016 at 10:22:45PM +0100, Georg Baum wrote: > Am 28.02.2016 um 18:22 schrieb Sven Hoexter: > >On Sun, Feb 28, 2016 at 11:42:52AM +0100, picca wrote: Hello Georg, > >>1) lyx try to create a $HOME/.lyx even if $HOME does not exist > >>2) it would be great to avoir creating this .lyx directory by default. > >While I agree that 1) is a bug 2) is a bit more complicated. > It is documented that LyX needs a user configuration directory. If the > default location does not fit, you can use the -userdir parameter. Where is > the problem? Would you like to fail in a different way if $HOME does not > exist? It would be easy to add a check for that, but I'd like to understand > the problem before doing anything. IMO there should be a check, maybe in the python script itself, to check if it can write to $HOME/.lyx at all. If not abort with an error message pointing to the -userdir option. I think using the -userdir option is also the way to go if you use lyx during build time in minimal build environments like sbuild chroots. > >LyX is not really intended to be used this way, it's more or less > >centered around the idea of an GUI use in a real user environment. > Most people do indeed use LyX that way, but using it via command line > without a GUI is an important use case as well (and works fine in general). Sorry I wasn't precise here, I used LyX + makefiles + git all the time. My point was more about the build chroots without a real user environment that is far away from some kind of "end user setup". Scrap the "GUI" from my sentence. Cheers, Sven
Bug#816173: [Pkg-lyx-devel] Bug#816173: Bug#816173: lyx: Lyx failed to start if the $HOME/.lyx does not exist
Am 28.02.2016 um 18:22 schrieb Sven Hoexter: On Sun, Feb 28, 2016 at 11:42:52AM +0100, picca wrote: Hi, while preparing my tango package, I need to build the documentation with lyx. For future reference, here is the d-d thread: https://lists.debian.org/debian-devel/2016/02/msg00454.html It seems that it is not allow to write outside the source directory except /tmp during the build process. I see at least two problems. 1) lyx try to create a $HOME/.lyx even if $HOME does not exist 2) it would be great to avoir creating this .lyx directory by default. While I agree that 1) is a bug 2) is a bit more complicated. It is documented that LyX needs a user configuration directory. If the default location does not fit, you can use the -userdir parameter. Where is the problem? Would you like to fail in a different way if $HOME does not exist? It would be easy to add a check for that, but I'd like to understand the problem before doing anything. LyX is not really intended to be used this way, it's more or less centered around the idea of an GUI use in a real user environment. Most people do indeed use LyX that way, but using it via command line without a GUI is an important use case as well (and works fine in general). It's part of the whole configuration problem, kind of a dublicate of #397464. Yes. Parts of the configuration in .the user directory are needed (they are expensive to calculate), other could be gathered by different mechanisms if somebody would take the time to implement that. Georg
