Re: Lyx 1.6.2 debian binaries (LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien])
Wolfgang Engelmann wrote: > Am Friday 03 April 2009 09:24:10 schrieb Guenter Milde: >> On 2009-04-02, Per Olofsson wrote: >>> FWIW, I just uploaded lyx 1.6.2 to Debian unstable. >> Thanks a lot. >> >> Günter > > Very good news. I was struggling with installing from sources -which is > probably a good idea in respect to the improvements, but I have to learn more > before I can do it. Thank you very much, Per I'm sorry for the delay - I'll try to be quicker next time.
Re: Lyx 1.6.2 debian binaries (LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien])
Am 03.04.2009, 00:46 Uhr, schrieb Per Olofsson : Thanks a lot, Per. Nina Nina Lafayette wrote: Am 24.03.2009, 15:29 Uhr, schrieb Guenter Milde : Hi folks, isn't there anybody who can put the debian binaries for Lyx 1.6.2 on a Web server? This would be great! FWIW, I just uploaded lyx 1.6.2 to Debian unstable. Should hit the mirrors soon. Thanks, Nina On 2009-03-24, rgheck wrote: Wolfgang Engelmann wrote: ... I wonder whether somebody has used the alien prg for the SuSe rpm package. Is it recommendable or better to use the source code? Once you get used to it, using the source is very easy. But until this, you may spend some time trying (I spent months). In fact, even better, download the 1.6 branch from svn and compile that. Then keep it up to date, recompile it every once in a while, and you'll always have the absolutely latest fixes, without waiting for a new release. Seconded. To do this, make sure you have the toolchain installed: autotools, make, gcc. You'll also need some devel packages, though I'd be surprised if pulling in the devel package for Qt4 wasn't enough to pull in the rest. Under Debian, you can install all that is required to compile lyx with `apt-get build-dep lyx`. Then make a directory for the sources and do this: # cd /my/src/dir # svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X # cd BRANCH_1_6_X # ./autogen.sh # ./configure --enable-build-type rel --prefix /usr/local ---that last is of course optional, but then you won't overwrite the LyX package. I use ./configure --with-version-suffix=16 --enable-build-type=release so that I can start the packed version (1.6.1 here) with `lyx` and the home-grown with `lyx16`. This has also the effect of using separate user LYXDIRS (~/.lyx vs. ~/.lyx16). The --prefix /usr/local seems to be the default. # make # sudo make install And there you go. Absolutely up to date. And for moving the binary to another machine: # "make DESTDIR=/tmp/lyx-svn install" and then make an archive of everything in /tmp/lyx-svn. Günter
Re: Lyx 1.6.2 debian binaries (LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien])
Am Friday 03 April 2009 09:24:10 schrieb Guenter Milde: > On 2009-04-02, Per Olofsson wrote: > > FWIW, I just uploaded lyx 1.6.2 to Debian unstable. > > Thanks a lot. > > Günter Very good news. I was struggling with installing from sources -which is probably a good idea in respect to the improvements, but I have to learn more before I can do it. Thank you very much, Per Wolfgang
Re: Lyx 1.6.2 debian binaries (LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien])
On 2009-04-02, Per Olofsson wrote: > FWIW, I just uploaded lyx 1.6.2 to Debian unstable. Thanks a lot. Günter
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien]
2009/4/2 Wolfgang Engelmann : > Am Tuesday 24 March 2009 15:29:12 schrieb Guenter Milde: > > I would like to install LyX1.6.2 - > if I try >> svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X > > it says the URL does not exist. Is the site down? When will it be up again? Are you behind proxy? SVN protocol itself does not work behind proxy, that is why I cannot checkout LyX source code @work. -- Manveru jabber: manv...@manveru.pl gg: 1624001 http://www.manveru.pl
Re: Lyx 1.6.2 debian binaries (LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien])
Nina Lafayette wrote: > Am 24.03.2009, 15:29 Uhr, schrieb Guenter Milde > : > > Hi folks, > > isn't there anybody who can put the debian binaries for Lyx 1.6.2 on a Web > server? This would be great! FWIW, I just uploaded lyx 1.6.2 to Debian unstable. Should hit the mirrors soon. > > Thanks, > Nina > >> On 2009-03-24, rgheck wrote: >>> Wolfgang Engelmann wrote: >> >> ... I wonder whether somebody has used the alien prg for the SuSe rpm package. Is it recommendable or better to use the source code? >> >>> Once you get used to it, using the source is very easy. >> >> But until this, you may spend some time trying (I spent months). >> >>> In fact, even better, download the 1.6 branch from svn and compile >>> that. Then keep it up to date, recompile it every once in a while, and >>> you'll always have the absolutely latest fixes, without waiting for a >>> new release. >> >> Seconded. >> >> >>> To do this, make sure you have the toolchain installed: autotools, make, >>> gcc. You'll also need some devel packages, though I'd be surprised if >>> pulling in the devel package for Qt4 wasn't enough to pull in the rest. >> >> Under Debian, you can install all that is required to compile lyx with >> `apt-get build-dep lyx`. >> >>> Then make a directory for the sources and do this: >>> # cd /my/src/dir >>> # svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X >>> # cd BRANCH_1_6_X >>> # ./autogen.sh >>> # ./configure --enable-build-type rel --prefix /usr/local >> >>> ---that last is of course optional, but then you won't overwrite the LyX >>> package. >> >> I use >> >> ./configure --with-version-suffix=16 --enable-build-type=release >> >> so that I can start the packed version (1.6.1 here) with `lyx` and the >> home-grown with `lyx16`. This has also the effect of using separate user >> LYXDIRS (~/.lyx vs. ~/.lyx16). The --prefix /usr/local seems to be the >> default. >> >>> # make >>> # sudo make install >> >>> And there you go. Absolutely up to date. >> >> And for moving the binary to another machine: >> >> # "make DESTDIR=/tmp/lyx-svn install" >> and then make an archive of everything in /tmp/lyx-svn. >> >> Günter >> > >
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien]
Wolfgang Engelmann wrote: Am Tuesday 24 March 2009 15:29:12 schrieb Guenter Milde: I would like to install LyX1.6.2 - if I try svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X it says the URL does not exist. Is the site down? When will it be up again? I just did this and it was fine. Try cut and paste rh
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien]
Am Tuesday 24 March 2009 15:29:12 schrieb Guenter Milde: I would like to install LyX1.6.2 - if I try > svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X it says the URL does not exist. Is the site down? When will it be up again? Wolfgang
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien] -SOLVED
On 26 Mar 2009, Guenter Milde wrote: > On 2009-03-26, Anthony Campbell wrote: > > > For some reason, though, I had to copy the resultant lyx executable to > > ~/bin myself; neither make install nor the deb file put an executable in > > place. > > By default, the prefix is /usr/local, so probably the executable ended up in > /usr/local/bin (if you did not give another option to ./configure). > Or you configured --with-version-suffix and this is appended to "lyx". > > Günter > Yes, I think that was it. Incidentally, I've now discovered why I was needing to put the path to Qt4 on the laptop. I didn't have the pkg-config package installed. Now that I have, lyx finds the library automatically. Perhaps it would be worth including a note about this in the INSTALL file? Anthony -- Anthony Campbell - a...@acampbell.org.uk Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles)
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien] -SOLVED
On 2009-03-26, Anthony Campbell wrote: > For some reason, though, I had to copy the resultant lyx executable to > ~/bin myself; neither make install nor the deb file put an executable in > place. By default, the prefix is /usr/local, so probably the executable ended up in /usr/local/bin (if you did not give another option to ./configure). Or you configured --with-version-suffix and this is appended to "lyx". Günter
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien] -SOLVED
On 25 Mar 2009, Anthony Campbell wrote: > On 25 Mar 2009, rgheck wrote: > > > Hard to know. The first thing I'd do is check to make sure libqt4-dev is > > installed, and find out where it is installed. Anyway, if you want to > > post the config.log, I can have a look. > > > > rh > > > libqt4-dev is installed. There doesn't seem to be one file; there are > several in /usr/share/lintian/overrides. Pointing configure to this > doesn't help. Here is config.log. It seems to have found several files > but at the end it fails. > > I had to cut some of it because the server rejected it initially as too > big, but I hopeI've kept the important bits, which seem to come at the > end. > > Anthony > I did a reinstall of qt4 and this time it created a directory in /usr/share. I pointed the lyx configure file to that and it worked. For some reason, though, I had to copy the resultant lyx executable to ~/bin myself; neither make install nor the deb file put an executable in place. Anthony -- Anthony Campbell - a...@acampbell.org.uk Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles)
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien]
On 25 Mar 2009, rgheck wrote:
> Hard to know. The first thing I'd do is check to make sure libqt4-dev is
> installed, and find out where it is installed. Anyway, if you want to
> post the config.log, I can have a look.
>
> rh
libqt4-dev is installed. There doesn't seem to be one file; there are
several in /usr/share/lintian/overrides. Pointing configure to this
doesn't help. Here is config.log. It seems to have found several files
but at the end it fails.
I had to cut some of it because the server rejected it initially as too
big, but I hopeI've kept the important bits, which seem to come at the
end.
Anthony
==
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by LyX configure 1.6.2, which was
generated by GNU Autoconf 2.63. Invocation command line was
$ ./configure
## - ##
## Platform. ##
## - ##
hostname = ithaca
uname -m = i686
uname -r = 2.6.28-1-686
uname -s = Linux
uname -v = #1 SMP Mon Feb 23 03:13:24 UTC 2009
/usr/bin/uname -p = unknown
/bin/uname -X = unknown
/bin/arch = unknown
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /bin
PATH: /usr/bin
PATH: /sbin
PATH: /usr/sbin
PATH: /usr/X11R6
PATH: /usr/X11R6/bin
PATH: /usr/local/bin
PATH: /home/ac/bin
PATH: /usr/games
## --- ##
## Core tests. ##
## --- ##
configure:2344: checking for build type
configure:2367: result: release
configure:2379: checking for version suffix
configure:2396: result:
configure:2406: checking build system type
configure:2424: result: i686-pc-linux-gnu
configure:2446: checking host system type
configure:2461: result: i686-pc-linux-gnu
configure:2483: checking target system type
configure:2498: result: i686-pc-linux-gnu
configure:2526: checking what packaging should be used
configure:2541: result: posix
configure:2609: checking whether to enable maintainer-specific portions of
Makefiles
configure:2618: result: no
configure:2649: checking for a BSD-compatible install
configure:2717: result: /usr/bin/install -c
configure:2728: checking whether build environment is sane
configure:2771: result: yes
configure:2796: checking for a thread-safe mkdir -p
configure:2835: result: /bin/mkdir -p
configure:2848: checking for gawk
configure:2864: found /usr/bin/gawk
configure:2875: result: gawk
configure:2886: checking whether make sets $(MAKE)
configure:2908: result: yes
configure:3125: checking for a Python interpreter with version >= 2.3.4
configure:3140: python -c import sys, string # split strings by '.' and convert
to numeric. Append some zeros # because we need at least 4 digits for the hex
conversion. minver = map(int, string.split('2.3.4', '.')) + [0, 0, 0] minverhex
= 0 for i in xrange(0, 4): minverhex = (minverhex << 8) + minver[i]
sys.exit(sys.hexversion < minverhex)
configure:3143: $? = 0
configure:3150: result: python
configure:3158: checking for python
configure:3176: found /usr/bin/python
configure:3188: result: /usr/bin/python
configure:3206: checking for python version
configure:3213: result: 2.5
configure:3225: checking for python platform
configure:3232: result: linux2
configure:3239: checking for python script directory
configure:3247: result: ${prefix}/lib/python2.5/site-packages
configure:3256: checking for python extension module directory
configure:3264: result: ${exec_prefix}/lib/python2.5/site-packages
configure:: checking for gcc
configure:3349: found /usr/bin/gcc
configure:3360: result: gcc
configure:3592: checking for C compiler version
configure:3600: gcc --version >&5
gcc (Debian 4.3.3-5) 4.3.3
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:3604: $? = 0
configure:3611: gcc -v >&5
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.3-5'
--with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3
--program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug
--enable-objc-gc --enable-mpfr --enable-targets=all --with-tune=generic
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu
--target=i486-linux-gnu
Thread model: posix
gcc version 4.3.3 (Debian 4.3.3-5)
configure:3615: $? = 0
configure:3622: gcc -V >&5
gcc: '-V' option must have argument
configure:3626: $? = 1
configure:3649: checking for C compiler default output file name
configure:3671: gccconftest.c >&5
configure:3675: $?
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien]
Anthony Campbell wrote: On 24 Mar 2009, rgheck wrote: Wolfgang Engelmann wrote: Since there seems to be no deb package of lyx 1.6.2 yet for debian, I wonder whether somebody has used the alien prg for the SuSe rpm package. Is it recommendable or better to use the source code? Once you get used to it, using the source is very easy. In fact, even better, download the 1.6 branch from svn and compile that. Then keep it up to date, recompile it every once in a while, and you'll always have the absolutely latest fixes, without waiting for a new release. Note that since this is branch, fixes only go in when they're regarded as safe---which doesn't of course guarantee that they are, though neither is 1.6.2 guaranteed to be safe, right? To do this, make sure you have the toolchain installed: autotools, make, gcc. You'll also need some devel packages, though I'd be surprised if pulling in the devel package for Qt4 wasn't enough to pull in the rest. Then make a directory for the sources and do this: # cd /my/src/dir # svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X # cd BRANCH_1_6_X # ./autogen.sh # ./configure --enable-build-type rel --prefix /usr/local ---that last is of course optional, but then you won't overwrite the LyX package. # make # sudo make install And there you go. Absolutely up to date. I tried this and it worked well on my desktop. When I tried it on my laptop it failed, saying it could not find Qt4. Both machines are running Debian Sid and in both I installed Qt4 in the same way, by installing libqt4-dev. It's not a huge problem since I have the deb package for lyx-1.6.1, but I'm curious about why there is this difference. I spent a long time looking at config.log but no illumination dawned. Hard to know. The first thing I'd do is check to make sure libqt4-dev is installed, and find out where it is installed. Anyway, if you want to post the config.log, I can have a look. rh
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien]
On 24 Mar 2009, rgheck wrote: > Wolfgang Engelmann wrote: >> Since there seems to be no deb package of lyx 1.6.2 yet for debian, I >> wonder whether somebody has used the alien prg for the SuSe rpm >> package. Is it recommendable or better to use the source code? >> >> > Once you get used to it, using the source is very easy. In fact, even > better, download the 1.6 branch from svn and compile that. Then keep it > up to date, recompile it every once in a while, and you'll always have > the absolutely latest fixes, without waiting for a new release. Note > that since this is branch, fixes only go in when they're regarded as > safe---which doesn't of course guarantee that they are, though neither > is 1.6.2 guaranteed to be safe, right? > > To do this, make sure you have the toolchain installed: autotools, make, > gcc. You'll also need some devel packages, though I'd be surprised if > pulling in the devel package for Qt4 wasn't enough to pull in the rest. > Then make a directory for the sources and do this: > # cd /my/src/dir > # svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X > # cd BRANCH_1_6_X > # ./autogen.sh > # ./configure --enable-build-type rel --prefix /usr/local > ---that last is of course optional, but then you won't overwrite the LyX > package. > # make > # sudo make install > And there you go. Absolutely up to date. > > Richard I tried this and it worked well on my desktop. When I tried it on my laptop it failed, saying it could not find Qt4. Both machines are running Debian Sid and in both I installed Qt4 in the same way, by installing libqt4-dev. It's not a huge problem since I have the deb package for lyx-1.6.1, but I'm curious about why there is this difference. I spent a long time looking at config.log but no illumination dawned. Anthony -- Anthony Campbell - a...@acampbell.org.uk Microsoft-free zone - Using Debian GNU/Linux http://www.acampbell.org.uk (blog, book reviews, and sceptical articles)
Re: Lyx 1.6.2 debian 64bit binaries (LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien])
Am 24.03.2009, 16:03 Uhr, schrieb Nina Lafayette : P.S.: A 64bit version of Lyx 1.6.2 for debian would be highly appreciated. Regards, Nina Am 24.03.2009, 15:29 Uhr, schrieb Guenter Milde : Hi folks, isn't there anybody who can put the debian binaries for Lyx 1.6.2 on a Web server? This would be great! Thanks, Nina On 2009-03-24, rgheck wrote: Wolfgang Engelmann wrote: ... I wonder whether somebody has used the alien prg for the SuSe rpm package. Is it recommendable or better to use the source code? Once you get used to it, using the source is very easy. But until this, you may spend some time trying (I spent months). In fact, even better, download the 1.6 branch from svn and compile that. Then keep it up to date, recompile it every once in a while, and you'll always have the absolutely latest fixes, without waiting for a new release. Seconded. To do this, make sure you have the toolchain installed: autotools, make, gcc. You'll also need some devel packages, though I'd be surprised if pulling in the devel package for Qt4 wasn't enough to pull in the rest. Under Debian, you can install all that is required to compile lyx with `apt-get build-dep lyx`. Then make a directory for the sources and do this: # cd /my/src/dir # svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X # cd BRANCH_1_6_X # ./autogen.sh # ./configure --enable-build-type rel --prefix /usr/local ---that last is of course optional, but then you won't overwrite the LyX package. I use ./configure --with-version-suffix=16 --enable-build-type=release so that I can start the packed version (1.6.1 here) with `lyx` and the home-grown with `lyx16`. This has also the effect of using separate user LYXDIRS (~/.lyx vs. ~/.lyx16). The --prefix /usr/local seems to be the default. # make # sudo make install And there you go. Absolutely up to date. And for moving the binary to another machine: # "make DESTDIR=/tmp/lyx-svn install" and then make an archive of everything in /tmp/lyx-svn. Günter
Re: Lyx 1.6.2 debian binaries (LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien])
Am 24.03.2009, 15:29 Uhr, schrieb Guenter Milde : Hi folks, isn't there anybody who can put the debian binaries for Lyx 1.6.2 on a Web server? This would be great! Thanks, Nina On 2009-03-24, rgheck wrote: Wolfgang Engelmann wrote: ... I wonder whether somebody has used the alien prg for the SuSe rpm package. Is it recommendable or better to use the source code? Once you get used to it, using the source is very easy. But until this, you may spend some time trying (I spent months). In fact, even better, download the 1.6 branch from svn and compile that. Then keep it up to date, recompile it every once in a while, and you'll always have the absolutely latest fixes, without waiting for a new release. Seconded. To do this, make sure you have the toolchain installed: autotools, make, gcc. You'll also need some devel packages, though I'd be surprised if pulling in the devel package for Qt4 wasn't enough to pull in the rest. Under Debian, you can install all that is required to compile lyx with `apt-get build-dep lyx`. Then make a directory for the sources and do this: # cd /my/src/dir # svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X # cd BRANCH_1_6_X # ./autogen.sh # ./configure --enable-build-type rel --prefix /usr/local ---that last is of course optional, but then you won't overwrite the LyX package. I use ./configure --with-version-suffix=16 --enable-build-type=release so that I can start the packed version (1.6.1 here) with `lyx` and the home-grown with `lyx16`. This has also the effect of using separate user LYXDIRS (~/.lyx vs. ~/.lyx16). The --prefix /usr/local seems to be the default. # make # sudo make install And there you go. Absolutely up to date. And for moving the binary to another machine: # "make DESTDIR=/tmp/lyx-svn install" and then make an archive of everything in /tmp/lyx-svn. Günter
Re: LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien]
On 2009-03-24, rgheck wrote: > Wolfgang Engelmann wrote: >> ... I wonder whether somebody has used the alien prg for the SuSe rpm >> package. Is it recommendable or better to use the source code? > Once you get used to it, using the source is very easy. But until this, you may spend some time trying (I spent months). > In fact, even better, download the 1.6 branch from svn and compile > that. Then keep it up to date, recompile it every once in a while, and > you'll always have the absolutely latest fixes, without waiting for a > new release. Seconded. > To do this, make sure you have the toolchain installed: autotools, make, > gcc. You'll also need some devel packages, though I'd be surprised if > pulling in the devel package for Qt4 wasn't enough to pull in the rest. Under Debian, you can install all that is required to compile lyx with `apt-get build-dep lyx`. > Then make a directory for the sources and do this: > # cd /my/src/dir > # svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X > # cd BRANCH_1_6_X > # ./autogen.sh > # ./configure --enable-build-type rel --prefix /usr/local > ---that last is of course optional, but then you won't overwrite the LyX > package. I use ./configure --with-version-suffix=16 --enable-build-type=release so that I can start the packed version (1.6.1 here) with `lyx` and the home-grown with `lyx16`. This has also the effect of using separate user LYXDIRS (~/.lyx vs. ~/.lyx16). The --prefix /usr/local seems to be the default. > # make > # sudo make install > And there you go. Absolutely up to date. And for moving the binary to another machine: # "make DESTDIR=/tmp/lyx-svn install" and then make an archive of everything in /tmp/lyx-svn. Günter
LyX Branch, self-compiled [was: lyx 1.6.2 for debian using rpm and alien]
Wolfgang Engelmann wrote: Since there seems to be no deb package of lyx 1.6.2 yet for debian, I wonder whether somebody has used the alien prg for the SuSe rpm package. Is it recommendable or better to use the source code? Once you get used to it, using the source is very easy. In fact, even better, download the 1.6 branch from svn and compile that. Then keep it up to date, recompile it every once in a while, and you'll always have the absolutely latest fixes, without waiting for a new release. Note that since this is branch, fixes only go in when they're regarded as safe---which doesn't of course guarantee that they are, though neither is 1.6.2 guaranteed to be safe, right? To do this, make sure you have the toolchain installed: autotools, make, gcc. You'll also need some devel packages, though I'd be surprised if pulling in the devel package for Qt4 wasn't enough to pull in the rest. Then make a directory for the sources and do this: # cd /my/src/dir # svn co svn://svn.lyx.org/lyx/lyx-devel/branches/BRANCH_1_6_X # cd BRANCH_1_6_X # ./autogen.sh # ./configure --enable-build-type rel --prefix /usr/local ---that last is of course optional, but then you won't overwrite the LyX package. # make # sudo make install And there you go. Absolutely up to date. Richard
