Re: [Pkg-lyx-devel] Linking with gold

Hi, Jean-Marc Lasgouttes skrev: Abdelrazak Younes you...@lyx.org writes: Because QtGui is a dynamic library it handles its dependency alone. What you say would be try if we did static linking. It seems to me that, in the old days, dynamic libraries requires extra -lFoo too. I think it

Re: [Pkg-lyx-devel] Linking with gold

Jean-Marc Lasgouttes skrev: BTW, is linking with gold a win with LyX? It's supposed to be faster, although I haven't tried it. I don't think it affects runtime speed though, only build speed. -- Pelle

Re: [Pkg-lyx-devel] Linking with gold

Hi, Jean-Marc Lasgouttes skrev: Abdelrazak Younes writes: Because QtGui is a dynamic library it handles its dependency alone. What you say would be try if we did static linking. It seems to me that, in the old days, dynamic libraries requires extra -lFoo too. I think it

Re: [Pkg-lyx-devel] Linking with gold

Jean-Marc Lasgouttes skrev: BTW, is linking with gold a win with LyX? It's supposed to be faster, although I haven't tried it. I don't think it affects runtime speed though, only build speed. -- Pelle

Re: [Pkg-lyx-devel] Linking with gold

Hi Sven, Sven Hoexter skrev: Oh and I've no profound knowledge of the issue so it's possible that the better solution would be to fix something in Qt's pkg-config in Debian. It's not Qt's fault -- lyx uses X11 libs directly in at least one place: src/frontends/qt4/GuiApplication.cpp -- Pelle

Re: [Pkg-lyx-devel] Linking with gold

Hi Sven, Sven Hoexter skrev: Oh and I've no profound knowledge of the issue so it's possible that the better solution would be to fix something in Qt's pkg-config in Debian. It's not Qt's fault -- lyx uses X11 libs directly in at least one place: src/frontends/qt4/GuiApplication.cpp -- Pelle

Re: signing releases

Hi, Jürgen Spitzmüller wrote: Jean-Marc Lasgouttes wrote: I guess we would need one key for you and one for Jose (we cannot share a LyX key). I have a key. But I guess it is not very authorative (due to missing counter- signs). Well, even if your keys are not signed by anyone, it still

Re: signing releases

Hi, Jürgen Spitzmüller wrote: > Jean-Marc Lasgouttes wrote: >> I guess we would need one key for you and one for Jose (we cannot share >> a LyX key). > > I have a key. But I guess it is not very authorative (due to missing counter- > signs). Well, even if your keys are not signed by anyone, it

signing releases

Hi LyX developers, Have you thought about GPG-signing the LyX tarballs? As a Debian packager, it would make me feel a bit safer :-) -- Pelle [please cc me on replies]

signing releases

Hi LyX developers, Have you thought about GPG-signing the LyX tarballs? As a Debian packager, it would make me feel a bit safer :-) -- Pelle [please cc me on replies]

Re: [Pkg-lyx-devel] Bug#475523: Any idea on #475523? - LyX unusable with Qt 4.4.0rc1-2

Hi, Sven Hoexter wrote: with Qt 4.4.0rc1-2 hitting unstable we noticed that LyX fails badly. I've no clue if it's a problem of LyX with the new Qt version or a problem within Qt 4.4. Maybe you can take a look at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475523 and give me a hint.

Re: [Pkg-lyx-devel] Bug#475523: Any idea on #475523? - LyX unusable with Qt 4.4.0rc1-2

Hi, Sven Hoexter wrote: > with Qt 4.4.0rc1-2 hitting unstable we noticed that LyX fails badly. I've > no clue if it's a problem of LyX with the new Qt version or a problem within > Qt 4.4. > Maybe you can take a look at > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475523 > and give me a

Re: xdg-open

rgheck wrote: Per Olofsson wrote: There is no mention of mimeopen in copy of xdg-open. Could it be another distro-specific patch? Sounds like it. Seems like a good patch, I should add it to the Debian package. Which distribution are you running? mimeopen seems like the program I

Re: xdg-open

rgheck wrote: > Per Olofsson wrote: >> There is no mention of mimeopen in copy of xdg-open. Could it be another >> distro-specific patch? >> >> > Sounds like it. Seems like a good patch, I should add it to the Debian package. Which distribution are you runni

Re: xdg-open

Sven Hoexter wrote: On Sat, Jan 05, 2008 at 06:36:50PM +0100, Pavel Sanda wrote: If it's really too much pain to fix xdg-open then I've to agree that it would make more sense to revert the change. have you some experience how much are xdg devs communicative about the run-mailcap thing ?

Re: xdg-open

Sven Hoexter wrote: On Sat, Jan 05, 2008 at 06:36:50PM +0100, Pavel Sanda wrote: If it's really too much pain to fix xdg-open then I've to agree that it would make more sense to revert the change. have you some experience how much are xdg devs communicative about the run-mailcap thing ?

Re: xdg-open

Sven Hoexter wrote: > On Sat, Jan 05, 2008 at 06:36:50PM +0100, Pavel Sanda wrote: > >>> If it's really too much pain to fix xdg-open then I've to agree that it >>> would make more sense to revert the change. >> have you some experience how much are xdg devs communicative about the >> run-mailcap

Re: xdg-open

Sven Hoexter wrote: > On Sat, Jan 05, 2008 at 06:36:50PM +0100, Pavel Sanda wrote: > >>> If it's really too much pain to fix xdg-open then I've to agree that it >>> would make more sense to revert the change. >> have you some experience how much are xdg devs communicative about the >> run-mailcap

Source for latex-xft-fonts?

Hi, There is a bug filed against the latex-xft-fonts Debian package about the lack of source code for it (http://bugs.debian.org/402148). This prevents the package from entering etch (the upcoming stable release of Debian). Apparently the fonts have been converted from the corresponding LaTeX

Re: [Pkg-lyx-devel] Re: Source for latex-xft-fonts?

John Levon: I've entirely forgotten how I did it, but it definitely involved some manual fixing of the fonts. I used some popular open-source font editor, which I've also forgotten, and I had to fix some stuff up if I remember rightly. Perhaps fontforge? I have no idea what sources they're

Source for latex-xft-fonts?

Hi, There is a bug filed against the latex-xft-fonts Debian package about the lack of source code for it (http://bugs.debian.org/402148). This prevents the package from entering etch (the upcoming stable release of Debian). Apparently the fonts have been converted from the corresponding LaTeX

Re: [Pkg-lyx-devel] Re: Source for latex-xft-fonts?

John Levon: > I've entirely forgotten how I did it, but it definitely involved some > manual fixing of the fonts. I used some popular open-source font editor, > which I've also forgotten, and I had to fix some stuff up if I remember > rightly. Perhaps fontforge? > I have no idea what "sources"

Re: [Pkg-lyx-devel] Bug#265030: Ispell and pspell still supported in 1.4?

Georg Baum: I agree with Enrico that in this particular case LyX is not to blame, but the problem is more general: LyX simply asks for a dictionary that is named after the document language and does not check at all whether that is a vlid dictionary name. That works well in many cases, but

Re: [Pkg-lyx-devel] Bug#265030: Ispell and pspell still supported in 1.4?

Georg Baum: > I agree with Enrico that in this particular case LyX is not to blame, but > the problem is more general: LyX simply asks for a dictionary that is > named after the document language and does not check at all whether that > is a vlid dictionary name. That works well in many cases,

Re: Bug#381622: [Pkg-lyx-devel] Re: [PATCH] bug 2741: configure.py is not run when using batch mode

Jean-Marc Lasgouttes: Per == Per Olofsson [EMAIL PROTECTED] writes: Per Jean-Marc Lasgouttes: What about that: mkdir /tmp/tempuserdir lyx -userdir /tmp/tempuserdir -e latex foo.lyx rm -rf /tmp/tempuserdir Per Yes, I think that's an acceptable workaround. Could you confirm

Re: Bug#381622: [Pkg-lyx-devel] Re: [PATCH] bug 2741: configure.py is not run when using batch mode

Jean-Marc Lasgouttes: > >>>>> "Per" == Per Olofsson <[EMAIL PROTECTED]> writes: > > Per> Jean-Marc Lasgouttes: > >> What about that: mkdir /tmp/tempuserdir lyx -userdir > >> /tmp/tempuserdir -e latex foo.lyx rm -rf /tmp/tempu

Re: [Pkg-lyx-devel] Re: [PATCH] bug 2741: configure.py is not run when using batch mode

Jean-Marc Lasgouttes: What about that: mkdir /tmp/tempuserdir lyx -userdir /tmp/tempuserdir -e latex foo.lyx rm -rf /tmp/tempuserdir Yes, I think that's an acceptable workaround. Per The best would be if configure.py was removed completely and Per everything was detected at runtime (or

Re: [Pkg-lyx-devel] Re: [PATCH] bug 2741: configure.py is not run when using batch mode

Jean-Marc Lasgouttes: > What about that: > mkdir /tmp/tempuserdir > lyx -userdir /tmp/tempuserdir -e latex foo.lyx > rm -rf /tmp/tempuserdir Yes, I think that's an acceptable workaround. > Per> The best would be if configure.py was removed completely and > Per> everything was detected at runtime

Re: [Pkg-lyx-devel] Re: [PATCH] bug 2741: configure.py is not run when using batch mode

Jean-Marc Lasgouttes: Thanks for the explanations. Could you try to see whether the patch I sent will fix the problem? I believe it should create a .lyx directory in root home directory and work correctly from there. Is it an acceptable solution? It's the correct fix, yes, but I don't

Re: [Pkg-lyx-devel] Re: [PATCH] bug 2741: configure.py is not run when using batch mode

Jean-Marc Lasgouttes: > Thanks for the explanations. Could you try to see whether the patch I > sent will fix the problem? I believe it should create a .lyx directory > in root home directory and work correctly from there. > > Is it an acceptable solution? It's the correct fix, yes, but I don't

Re: [Pkg-lyx-devel] Re: escaping the - in man.lyx

Jean-Marc Lasgouttes: Where can I read about this - vs. \- thing? I can't find it right now, but basically the difference is that - generates a hyphen, which is a different character when running man in a UTF-8 locale. This creates problems when you search manual pages or cut'n'paste because you

Re: [Pkg-lyx-devel] Re: escaping the - in man.lyx

Jean-Marc Lasgouttes: > Where can I read about this "-" vs. "\-" thing? I can't find it right now, but basically the difference is that "-" generates a hyphen, which is a different character when running man in a UTF-8 locale. This creates problems when you search manual pages or cut'n'paste

Re: [Pkg-lyx-devel] Let's get the Lyx Debian pkg back in sync with upstream

Hi, I'm the one who did the last NMU of LyX. Sven Hoexter: So I'm willing to take it over BUT my experience with Debian packaging is still quite low and limited to small packages[2]. Additional I've not followed the Lyx development for the last ~2 years. So any help would be highly

Re: [Pkg-lyx-devel] Let's get the Lyx Debian pkg back in sync with upstream

Hi, I'm the one who did the last NMU of LyX. Sven Hoexter: > So I'm willing to take it over BUT my experience with Debian > packaging is still quite low and limited to small > packages[2]. Additional I've not followed the Lyx development for > the last ~2 years. So any help would be highly