The new pre-release version is released, and while it isn't ready for general consumption I think it would be better to prepare the ebuild in advance and have it masked. :-)
Created attachment 78044 [details] lyx-1.4.0_pre3.ebuild This is a simple but working ebuild based on the one for lyx-1.3.6 Stripped out all CJK stuff as I don't have patches or any clue about it. Added GTK support. Using it is fun :)
Created attachment 78270 [details] lyx-1.4.0_pre3.ebuild Forgot to depend on xforms in case of !qt? || gtk?
The ebuild as is did not work for me. I had to change to the following code: if use qt ; then set-qtdir 3 myconf="$myconf --with-frontend=qt --with-qt-dir=${QTDIR}" ; fi Otherwise configure would complain that --with-frontend was not set and stop on. Aside from this, the ebuild worked great for me. Also, Lyx-1.4 now has change tracking. Although the change-tracking effects are seen within the LyX editor itself, dvipost is required in order to export the change-tracking markups to the postscript output, using dvips. Maybe the lyx-1.4 ebuild should add a dependency on "dvipost"?
Created attachment 78576 [details] lyx-1.4.0_pre3.ebuild Fix for previous comment Disabled GTK as it's not feature complete
(In reply to comment #1) > Stripped out all CJK stuff as I don't have patches or any clue about it. Just a note for future work on this, CJK support hasn't advanced beyond 1.3.6 at the time of writing.
1.4.0 is released and "stable" in the LyX repositories as of today, March 8, 2006. I've been running 1.4.0pre3 for about a week with no issues, and I just downloaded their provisional 1.4.0 a day or so ago, also running without issues. I'm not sure what has to be done with the ebuilds, but this is ready to go on x86 as far as I can tell.
I think we still need to wait for the CJK patches. It would bother a lot of users if we drop support for CJK in lyx. I have opened a bug a lyx asking them to merge the CJK patches so they maintain them, and if all goes well we wont have this much trouble on the next bump. http://bugzilla.lyx.org/show_bug.cgi?id=2360
Created attachment 81765 [details] Updated ebuild for 1.4.0 (now released) I have just modified the ebuild to point to the official lyx ftp server (not the devel one)
I have got a WONTFIX resolution on the bug at lyx: "The plan for 1.5 is to support unicode natively and thus hopefully subsume CJK-LyX functionality. There is little chance that the patches will be integrated as they are. They will however be used as a hint of the areas we need to cover. As far as 1.4.x is concerned, we will definitely not be able to do what the maintainers cannot do themselves. I surely hope that CJK-LyX 1.4 will happen soon..." We can't wait until lyx 1.5 and I think we can't wait much longer on the CJK patches. Can we strip the CJK patches from 1.4.0 and insert a notice to cjk users that they should stick to 1.3.6 (until either 1.5.0 or CJK patches get updated). CJK-herd please gives us your opinion.
It would be good to move this into portage and mark it as stable. What can be done to remove the delay?
(In reply to comment #9) > I have got a WONTFIX resolution on the bug at lyx: > > "The plan for 1.5 is to support unicode natively and thus hopefully subsume > CJK-LyX functionality. There is little chance that the patches will be > integrated as they are. They will however be used as a hint of the areas we > need > to cover. > > As far as 1.4.x is concerned, we will definitely not be able to do what the > maintainers cannot do themselves. > > I surely hope that CJK-LyX 1.4 will happen soon..." > > We can't wait until lyx 1.5 and I think we can't wait much longer on the CJK > patches. > Can we strip the CJK patches from 1.4.0 and insert a notice to cjk users that > they should stick to 1.3.6 (until either 1.5.0 or CJK patches get updated). > CJK-herd please gives us your opinion. > Looks like none of the lyx maintainers can even read CJK. The current -cjk patch ing strategy is to force all cjk text to use special fonts. It's very ugly to me. CJK is so much different from European languages. I hope the unicode scheme would work, but still doubt it will do the trick, if all lyx maintainers know phonetic languages only. (Japanese is phonetic too, but it uses Chinese characters)
(In reply to comment #4) > Created an attachment (id=78576) [edit] > lyx-1.4.0_pre3.ebuild > Fix for previous comment > Disabled GTK as it's not feature complete Work here with gtk gui (amd64).
> > Disabled GTK as it's not feature complete > Work here with gtk gui (amd64). Yes, GTK works and seems to be quite stable, BUT "not feature complete" means that some gui options are completely missing if you compile against GTK. When I tried it last (version 1.4.0-pre3) the dialogs for document settings and bibliography were fairly incomplete and hardly usable for my taste. The project's gui state page still shows some holes which means "not implemented yet and nobody is currently working on this: http://www.lyx.org/devel/guii.php Although I personally prefer GTK, I would keep it commented out as long as they didn't catch up with QT. Otherwise people just get annoyed.
I have added a slightly modified 1.4.0 ebuild to CVS. I have dropped CJK for the moment, but the ebuild informs the user if he or she has the cjk use flag set.
*** Bug 119526 has been marked as a duplicate of this bug. ***
