Re: Windows Installers: TESTING ONLY
On 05/31/2018 06:14 PM, Andrew Parsloe wrote: > On 16/05/2018 3:33 p.m., Richard Kimberly Heck wrote: >> I have finally managed to build Windows installers for 2.3.0. They can >> be found here: >> >> http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ >> >> Let me emphasize again that >> >> THESE ARE FOR TESTING ONLY >> >> I have tested them a little bit myself, but not a whole lot. They seem >> to work, basically---I compiled the tutorial---but that's as far as I'm >> going to go in vouching for them. My understanding of the installer code >> is pretty basic at this point. >> >> The executables were cross-compiled using MinGW on Linux. So these are >> not at all the same binaries that we have previously been distributing. >> The installers themselves, however, are pretty much the same, though >> without the "Update MiKTeX" code, which has just been commented out. If >> we want to include it, but issue some kind of warning, then I think that >> will need to be translated. I know where to put the translated strings, >> but I'm not entirely sure how to get them from the translators, and that >> will of course take time. >> >> Longer term, I have some thoughts about how to improve our situation on >> Windows, and there's been vigorous discussion over on the user list. But >> I'll save that for after we get an installer for 2.3.x. >> >> Riki >> >> PS Certainly one thing I've learned is that installing LyX with MikTeX >> takes *forever*, and I've got a fast internet connection. It would be >> nice to know what packages we need to install to compile the User Guide, >> etc, and just install those, rather than every single package LyX could >> possibly need. This is not trivial, since some of those are font >> definitions. >> > I've installed the 104 installer on a windows 7 system. The icon > missing with the 103 installer is now present. LyX seems to be working > -- it certainly displays the help docs correctly. Thanks for the report. I'm hoping to finalize all this over the next week. Riki
Re: Windows Installers: TESTING ONLY
On 16/05/2018 3:33 p.m., Richard Kimberly Heck wrote: I have finally managed to build Windows installers for 2.3.0. They can be found here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Let me emphasize again that THESE ARE FOR TESTING ONLY I have tested them a little bit myself, but not a whole lot. They seem to work, basically---I compiled the tutorial---but that's as far as I'm going to go in vouching for them. My understanding of the installer code is pretty basic at this point. The executables were cross-compiled using MinGW on Linux. So these are not at all the same binaries that we have previously been distributing. The installers themselves, however, are pretty much the same, though without the "Update MiKTeX" code, which has just been commented out. If we want to include it, but issue some kind of warning, then I think that will need to be translated. I know where to put the translated strings, but I'm not entirely sure how to get them from the translators, and that will of course take time. Longer term, I have some thoughts about how to improve our situation on Windows, and there's been vigorous discussion over on the user list. But I'll save that for after we get an installer for 2.3.x. Riki PS Certainly one thing I've learned is that installing LyX with MikTeX takes *forever*, and I've got a fast internet connection. It would be nice to know what packages we need to install to compile the User Guide, etc, and just install those, rather than every single package LyX could possibly need. This is not trivial, since some of those are font definitions. I've installed the 104 installer on a windows 7 system. The icon missing with the 103 installer is now present. LyX seems to be working -- it certainly displays the help docs correctly. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: Windows Installers: TESTING ONLY
Le 21 mai 2018 10:38:45 PM Jean-Marc Lasgouttes a écrit : Le 21/05/2018 à 22:36, Jean-Pierre a écrit : All the docs seem to compile all right, but displays of the pdfs fail by lack of a pdf reader :-( Incredible! I use this win10 seldomly, I have a dual boot with a Debian on this machine, that's why it is quite raw. I guess I would have installed a pdf reader if I had to use it seriously. This is strange, since Edge reads pdfs nowadays. So, how to make lyx find Edge ? Btw, I had a first try where I made a basic install of MiKTeX. Then it took a lot of time to install latex packages on the fly, I gave up after half an hour. So the full install must be chosen (I was offline when I performed the full install and the subsequent lyx install and testing). -- Jean-Pierre
Re: Windows Installers: TESTING ONLY
On 05/21/2018 04:38 PM, Jean-Marc Lasgouttes wrote: > Le 21/05/2018 à 22:36, Jean-Pierre a écrit : >> All the docs seem to compile all right, but displays of the pdfs fail >> by lack of a pdf reader :-( Incredible! >> I use this win10 seldomly, I have a dual boot with a Debian on this >> machine, that's why it is quite raw. I guess I would have installed a >> pdf reader if I had to use it seriously. > > This is strange, since Edge reads pdfs nowadays. I had to go into the Windows settings stuff and fiddle with the default PDF reader, and then it worked. Maybe something has changed in Windows 10 about where that's stored in the registry? Riki
Re: Windows Installers: TESTING ONLY
Le 21/05/2018 à 22:36, Jean-Pierre a écrit : All the docs seem to compile all right, but displays of the pdfs fail by lack of a pdf reader :-( Incredible! I use this win10 seldomly, I have a dual boot with a Debian on this machine, that's why it is quite raw. I guess I would have installed a pdf reader if I had to use it seriously. This is strange, since Edge reads pdfs nowadays. JMarc
Re: Windows Installers: TESTING ONLY
Le 19 mai 2018 10:59:21 Jean-Marc Lasgouttes a écrit There is also ProTeXt (https://www.tug.org/protext/), which seems to be a complete MikTeX distribution, weighing 2.6G. I used Protext 12 years ago as a tool to install MiKTeX (it's distributed by TUG, but it contains a part of MiKTeX in fact). I tried it together with Riki's installer, here is a record of the test on a quite fast laptop under win10: * 1h50 to download the 2.6 Go on my 400kb/s internet connection; * a few minutes to extract ProTeXt from the download; * half an hour to install MiKTeX; * 10 minutes to install LyX. All the docs seem to compile all right, but displays of the pdfs fail by lack of a pdf reader :-( Incredible! I use this win10 seldomly, I have a dual boot with a Debian on this machine, that's why it is quite raw. I guess I would have installed a pdf reader if I had to use it seriously. -- Jean-Pierre
Re: Windows Installers: TESTING ONLY
On 19/05/2018 8:59 p.m., Jean-Marc Lasgouttes wrote: Le 16/05/2018 à 19:48, Richard Kimberly Heck a écrit : It seems to me that there are two kinds of issues. One is what (if anything) we install, and the other is what happens after that. I think the "auto-install packages" feature of MiKTeX is great for people who don't want to get their hands too dirty, and Uwe was always right that we should try our best to help those folks. The problem, to my mind, is how this interacts with configure.py: Because of how we test for packages, I think, when we configure the first time, MiKTeX installs everything we test for. Which takes forever, and really doesn't make that much sense. I think we should remove all tests in configure.py besides what is actually needed in our code and and makes our behavior different. If there is a Packages list that installs everything in the MikTeX installer, this is good. I am surprised that it is still slow, though (maybe all this proves is that MikTeX is not appropriate for what we want to achieve). There is also ProTeXt (https://www.tug.org/protext/), which seems to be a complete MikTeX distribution, weighing 2.6G. Also, MikTeX can be installed as basic, essential or complete, and can be installed silently too. https://miktex.org/howto/deploy-miktex JMarc Installing MiKTeX packages on the fly is slow, but installing the basic MiKTeX distribution and then adding further packages is quite an efficient process, or would be if there were a readily available list of packages to load, for example to compile the help docs. There seems to be no correspondence between what is listed under Help > LaTeX configuration, and the yellow notes at the start of some of the docs listing packages necessary for compilation (and these haven't always been complete). When I discovered LyX (my very first LyX doc, titled newfile1.lyx, is dated 1 July 2007) I was using dial-up. Downloading even the basic MiKTeX was quite a challenge, but after that, downloading the occasional package, as needed, was quite feasible. Andrew --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: Windows Installers: TESTING ONLY
Le 16/05/2018 à 19:48, Richard Kimberly Heck a écrit : It seems to me that there are two kinds of issues. One is what (if anything) we install, and the other is what happens after that. I think the "auto-install packages" feature of MiKTeX is great for people who don't want to get their hands too dirty, and Uwe was always right that we should try our best to help those folks. The problem, to my mind, is how this interacts with configure.py: Because of how we test for packages, I think, when we configure the first time, MiKTeX installs everything we test for. Which takes forever, and really doesn't make that much sense. I think we should remove all tests in configure.py besides what is actually needed in our code and and makes our behavior different. If there is a Packages list that installs everything in the MikTeX installer, this is good. I am surprised that it is still slow, though (maybe all this proves is that MikTeX is not appropriate for what we want to achieve). There is also ProTeXt (https://www.tug.org/protext/), which seems to be a complete MikTeX distribution, weighing 2.6G. Also, MikTeX can be installed as basic, essential or complete, and can be installed silently too. https://miktex.org/howto/deploy-miktex JMarc
Re: Windows Installers: TESTING ONLY
Am Donnerstag, den 17.05.2018, 19:14 -0400 schrieb Richard Kimberly Heck: > Is there a concrete proposal to be made here? I.e., that the 'bundle' > installer should install TeXLive? And default to 'medium' (if we can > make it do that)? I can't make a fair judgment, since I really don't know MikTeX, and I also don't know whether TL on Windows works as Win users expect it. However, I think the installer (and to some extend even LyX itself) has been tied much too strong to a specific LaTeX distribution and its needs. Jürgen signature.asc Description: This is a digitally signed message part
Re: Windows Installers: TESTING ONLY
Le 16/05/2018 à 05:33, Richard Kimberly Heck a écrit : PS Certainly one thing I've learned is that installing LyX with MikTeX takes *forever*, and I've got a fast internet connection. It would be nice to know what packages we need to install to compile the User Guide, etc, and just install those, rather than every single package LyX could possibly need. This is not trivial, since some of those are font definitions. I have tried several times to convince Uwe to take a look at the MikTeX API that allows to download packages. This has to be faster than relying on \input hijacking. If it is not then something is seriously broken with MikTeX. JMarc
Re: Windows Installers: TESTING ONLY
On 05/18/2018 07:56 AM, Pavel Sanda wrote: > Richard Kimberly Heck wrote: >> Another possibility is to abandon the bundle installer and tell people >> they need to install a TeX distribution (and here are some links) >> before installing LyX. > Maybe the best option initially is it to keep it as simple as possible. I am > not sure how much rewarding is it for you in the long term to care about > possible issues with LaTeX distribution. Yes, that's more an issue for later. > If someone else joins the party, he can start doing it later (though somewhat > ironically your attempt to make the installers on your own prevents folks > like that to appear. I think ppl usually needs some itch to start new > enterprise and when some sort of installer is already available, well... ;) I thought about that. I'm intending, once this has been released, to raise some questions about how to proceed. E.g., posting a message to lyx-users, and maybe on the website, asking for help. In light of > What could help is some wiki page clearly explaining steps how to create > the current installer, so the initial learning curve is easy and potential > contributor does not need to reinvent the wheel like you did now. ...the time commitment won't be that great, and I'm happy to provide backup and help to figure out whatever issues might arise. We may also need to figure out what to do about the doucmentation and the translations, which Uwe largely handles. I'm not quite sure what his status is at this point. Riki
Re: Windows Installers: TESTING ONLY
Richard Kimberly Heck wrote: > Another possibility is to abandon the bundle installer and tell people > they need to install a TeX distribution (and here are some links) > before installing LyX. Maybe the best option initially is it to keep it as simple as possible. I am not sure how much rewarding is it for you in the long term to care about possible issues with LaTeX distribution. If someone else joins the party, he can start doing it later (though somewhat ironically your attempt to make the installers on your own prevents folks like that to appear. I think ppl usually needs some itch to start new enterprise and when some sort of installer is already available, well... ;) What could help is some wiki page clearly explaining steps how to create the current installer, so the initial learning curve is easy and potential contributor does not need to reinvent the wheel like you did now. Pavel
Re: Windows Installers: TESTING ONLY
On 05/17/2018 12:49 AM, Jean-Marc Lasgouttes wrote: > Le 16 mai 2018 23:33:45 GMT+02:00, Richard Kimberly Heck a > écrit : >> Yes, well, now there will be no console messages again, since people >> won't see the console at all. It would be nice if this were something >> one could set at runtime, rather than at compile time. I mentioned the >> possibility of a devel build, and certainly there one would want to see >> the console, though in that case I can just give this option >> >> Riki > There is the message pane, and we could send this data to a file in user dir > too. I guess maybe I need to experiment with the debug build on Windows. Maybe there's something like what happens on OSX, that you get a backtrace when you get a crash. Riki
Re: Windows Installers: TESTING ONLY
On 05/17/2018 03:30 AM, Jürgen Spitzmüller wrote: > Am Mittwoch, den 16.05.2018, 13:48 -0400 schrieb Richard Kimberly Heck: >> It seems to me that there are two kinds of issues. One is what (if >> anything) we install, and the other is what happens after that. I >> think the "auto-install packages" feature of MiKTeX is great for people who >> don't want to get their hands too dirty, and Uwe was always right >> that we should try our best to help those folks. > Well, there's texliveonfly for people wanting that: > https://ctan.org/pkg/texliveonfly Yes, that basically duplicates the MiKTeX feature. >> The problem, to my mind, is >> how this interacts with configure.py: Because of how we test for >> packages, I think, when we configure the first time, MiKTeX installs >> everything we test for. Which takes forever, and really doesn't make >> that much sense. (Actually, there's a list of packages to install in >> Packages.txt that's used to tell MiKTeX to install a bunch of stuff >> before we configure, but what it does is install everything that >> configure.py would install.) Maybe an option, then, would be to limit >> this list to stuff that is needed for e.g. compiling the >> documentation, >> and figure out some way to avoid installing everything on >> configuration. > That's the point. This "feature" causes more problems that it helps. > And our layouts are still cluttered with style and class requirements > just for the sake of this doubtful thing. We should remove those as > soon as we have switched to TeXLive. Is there a concrete proposal to be made here? I.e., that the 'bundle' installer should install TeXLive? And default to 'medium' (if we can make it do that)? Another possibility is to abandon the bundle installer and tell people they need to install a TeX distribution (and here are some links) before installing LyX. The non-bundled installer already does something like this, though it will let people proceed without LaTeX if they really want to do that. Riki
Re: Windows Installers: TESTING ONLY
Am Mittwoch, den 16.05.2018, 13:48 -0400 schrieb Richard Kimberly Heck: > It seems to me that there are two kinds of issues. One is what (if > anything) we install, and the other is what happens after that. I > think > the "auto-install packages" feature of MiKTeX is great for people who > don't want to get their hands too dirty, and Uwe was always right > that > we should try our best to help those folks. Well, there's texliveonfly for people wanting that: https://ctan.org/pkg/texliveonfly > The problem, to my mind, is > how this interacts with configure.py: Because of how we test for > packages, I think, when we configure the first time, MiKTeX installs > everything we test for. Which takes forever, and really doesn't make > that much sense. (Actually, there's a list of packages to install in > Packages.txt that's used to tell MiKTeX to install a bunch of stuff > before we configure, but what it does is install everything that > configure.py would install.) Maybe an option, then, would be to limit > this list to stuff that is needed for e.g. compiling the > documentation, > and figure out some way to avoid installing everything on > configuration. That's the point. This "feature" causes more problems that it helps. And our layouts are still cluttered with style and class requirements just for the sake of this doubtful thing. We should remove those as soon as we have switched to TeXLive. Jürgen signature.asc Description: This is a digitally signed message part
Re: Windows Installers: TESTING ONLY
Am Mittwoch, den 16.05.2018, 18:54 +0200 schrieb Pavel Sanda: > Jürgen Spitzmüller wrote: > > Am Mittwoch, den 16.05.2018, 10:09 -0400 schrieb Richard Kimberly > > Heck: > > > The issue is that the basic MiKTeX install gives one very little. > > > Not > > > enough even to compile the Introduction, largely due to font > > > metric > > > files. > > > > > > > What install choices we have with TeXLive? Bundling 4gb of data > > > > is > > > > not an > > > > option, but there might be small installer which can be > > > > conditioned > > > > on base > > > > installation, without docs and we would be suddenly in the > > > > realm of > > > > 50-200mb. > > > > TeXLive provides a variety of "schemes": > > https://tug.org/texlive/doc/texlive-en/texlive-en.html#x1-250003.2. > > 2 > > I looked at the page, but it was not clear to me if the "scheme" is > configurable by us, ie. launching installer with preselected > lyx-friendly scheme is possible. What seems related is the "profile" > commandline switch. Yes, --profile allows us to let TL install a scheme we have customized in a texlive.profile file. However, I wonder why we need to treat Windows users like children and not let them select themselves which scheme to install (we can still recommend them to install at least "medium" if they want our docs to be compilable. Jürgen > > Pavel signature.asc Description: This is a digitally signed message part
Re: Windows Installers: TESTING ONLY
Am Mittwoch, den 16.05.2018, 20:01 +0200 schrieb Kornel Benko: > > It looks like it's due to my using -DLYX_CONSOLE=FORCE, which was > in the > > xmingw file. > > > > Riki > > > > That's from me I suppose. We had reports about no console-messages > for Windows-lyx. > This was a try... apparently wrong. https://www.lyx.org/trac/ticket/8134 Jürgen signature.asc Description: This is a digitally signed message part
Re: Windows Installers: TESTING ONLY
Le 16 mai 2018 23:33:45 GMT+02:00, Richard Kimberly Heck a écrit : >Yes, well, now there will be no console messages again, since people >won't see the console at all. It would be nice if this were something >one could set at runtime, rather than at compile time. I mentioned the >possibility of a devel build, and certainly there one would want to see >the console, though in that case I can just give this option > >Riki There is the message pane, and we could send this data to a file in user dir too. JMarc
Re: Windows Installers: TESTING ONLY
On 05/16/2018 02:01 PM, Kornel Benko wrote: > > Am Mittwoch, 16. Mai 2018 13:23:52 CEST schrieb Richard Kimberly Heck > : > > > On 05/16/2018 12:30 PM, Pavel Sanda wrote: > > > > Richard Kimberly Heck wrote: > > > >>> 1. When starting LyX, a command window is presented and retained. > > > >>> Closing the command window closes LyX. > > > >> I saw this, too, on Windows 10, but did not know it was unusual. > I did > > > >> not change anything in the installer that should have affected this. > > > > IIRC there used to be whole routine hidden somewhere in nsi > scripts to take > > > > care of hiding the console (our app is launched as a console one). > > > > > > It looks like it's due to my using -DLYX_CONSOLE=FORCE, which was in the > > > xmingw file. > > > > > > Riki > > > > > > > That's from me I suppose. We had reports about no console-messages for > Windows-lyx. > > This was a try... apparently wrong. > Yes, well, now there will be no console messages again, since people won't see the console at all. It would be nice if this were something one could set at runtime, rather than at compile time. I mentioned the possibility of a devel build, and certainly there one would want to see the console, though in that case I can just give this option Riki
Re: Windows Installers: TESTING ONLY
Richard Kimberly Heck wrote: > It seems to me that there are two kinds of issues. One is what (if > anything) we install, and the other is what happens after that. I think > the "auto-install packages" feature of MiKTeX is great for people who > don't want to get their hands too dirty, and Uwe was always right that > we should try our best to help those folks. The problem, to my mind, is > how this interacts with configure.py: Because of how we test for > packages, I think, when we configure the first time, MiKTeX installs > everything we test for. Which takes forever, and really doesn't make > that much sense. (Actually, there's a list of packages to install in > Packages.txt that's used to tell MiKTeX to install a bunch of stuff > before we configure, but what it does is install everything that > configure.py would install.) Maybe an option, then, would be to limit > this list to stuff that is needed for e.g. compiling the documentation, > and figure out some way to avoid installing everything on configuration. I don't really have much opinion about the particular solution if the installation occurs within minuttes... > While we're at this, it occurred to me that maybe a "devel" build would > be useful, too, that we could direct users to if they're having > problems, and we need more debugging info. Yes, that should be trivial if mingw build is functioning. Pavel
Re: Windows Installers: TESTING ONLY
Am Mittwoch, 16. Mai 2018 13:23:52 CEST schrieb Richard Kimberly Heck : > On 05/16/2018 12:30 PM, Pavel Sanda wrote: > > Richard Kimberly Heck wrote: > >>> 1. When starting LyX, a command window is presented and retained. > >>> Closing the command window closes LyX. > >> I saw this, too, on Windows 10, but did not know it was unusual. I did > >> not change anything in the installer that should have affected this. > > IIRC there used to be whole routine hidden somewhere in nsi scripts to take > > care of hiding the console (our app is launched as a console one). > > It looks like it's due to my using -DLYX_CONSOLE=FORCE, which was in the > xmingw file. > > Riki > That's from me I suppose. We had reports about no console-messages for Windows-lyx. This was a try... apparently wrong. Kornel signature.asc Description: This is a digitally signed message part.
Re: Windows Installers: TESTING ONLY
On 05/16/2018 12:54 PM, Pavel Sanda wrote: > Jürgen Spitzmüller wrote: >> Am Mittwoch, den 16.05.2018, 10:09 -0400 schrieb Richard Kimberly Heck: >>> The issue is that the basic MiKTeX install gives one very little. Not >>> enough even to compile the Introduction, largely due to font metric >>> files. >>> What install choices we have with TeXLive? Bundling 4gb of data is not an option, but there might be small installer which can be conditioned on base installation, without docs and we would be suddenly in the realm of 50-200mb. >> TeXLive provides a variety of "schemes": >> https://tug.org/texlive/doc/texlive-en/texlive-en.html#x1-250003.2.2 > I looked at the page, but it was not clear to me if the "scheme" is > configurable by us, ie. launching installer with preselected > lyx-friendly scheme is possible. What seems related is the "profile" > commandline switch. It seems to me that there are two kinds of issues. One is what (if anything) we install, and the other is what happens after that. I think the "auto-install packages" feature of MiKTeX is great for people who don't want to get their hands too dirty, and Uwe was always right that we should try our best to help those folks. The problem, to my mind, is how this interacts with configure.py: Because of how we test for packages, I think, when we configure the first time, MiKTeX installs everything we test for. Which takes forever, and really doesn't make that much sense. (Actually, there's a list of packages to install in Packages.txt that's used to tell MiKTeX to install a bunch of stuff before we configure, but what it does is install everything that configure.py would install.) Maybe an option, then, would be to limit this list to stuff that is needed for e.g. compiling the documentation, and figure out some way to avoid installing everything on configuration. While we're at this, it occurred to me that maybe a "devel" build would be useful, too, that we could direct users to if they're having problems, and we need more debugging info. Riki
Re: Windows Installers: TESTING ONLY
On 05/16/2018 12:33 PM, Jürgen Spitzmüller wrote: > Am Dienstag, den 15.05.2018, 23:33 -0400 schrieb Richard Kimberly Heck: >> I have finally managed to build Windows installers for 2.3.0. > Just for the records, your efforts to get this back on track are highly > appreciated. I hope we can sort out the remaining problems. It's been worth learning a bit of this, I think. And I never can refuse a challenge Riki
Re: Windows Installers: TESTING ONLY
On 05/16/2018 12:30 PM, Pavel Sanda wrote: > Richard Kimberly Heck wrote: >>> 1. When starting LyX, a command window is presented and retained. >>> Closing the command window closes LyX. >> I saw this, too, on Windows 10, but did not know it was unusual. I did >> not change anything in the installer that should have affected this. > IIRC there used to be whole routine hidden somewhere in nsi scripts to take > care of hiding the console (our app is launched as a console one). It looks like it's due to my using -DLYX_CONSOLE=FORCE, which was in the xmingw file. Riki
Re: Windows Installers: TESTING ONLY
Jürgen Spitzmüller wrote: > Am Mittwoch, den 16.05.2018, 10:09 -0400 schrieb Richard Kimberly Heck: > > The issue is that the basic MiKTeX install gives one very little. Not > > enough even to compile the Introduction, largely due to font metric > > files. > > > > > What install choices we have with TeXLive? Bundling 4gb of data is > > > not an > > > option, but there might be small installer which can be conditioned > > > on base > > > installation, without docs and we would be suddenly in the realm of > > > 50-200mb. > > TeXLive provides a variety of "schemes": > https://tug.org/texlive/doc/texlive-en/texlive-en.html#x1-250003.2.2 I looked at the page, but it was not clear to me if the "scheme" is configurable by us, ie. launching installer with preselected lyx-friendly scheme is possible. What seems related is the "profile" commandline switch. Pavel
Re: Windows Installers: TESTING ONLY
Am Mittwoch, den 16.05.2018, 10:09 -0400 schrieb Richard Kimberly Heck: > The issue is that the basic MiKTeX install gives one very little. Not > enough even to compile the Introduction, largely due to font metric > files. > > > What install choices we have with TeXLive? Bundling 4gb of data is > > not an > > option, but there might be small installer which can be conditioned > > on base > > installation, without docs and we would be suddenly in the realm of > > 50-200mb. TeXLive provides a variety of "schemes": https://tug.org/texlive/doc/texlive-en/texlive-en.html#x1-250003.2.2 The medium scheme seems appropropriate For the Windows (net) installer, see: https://tug.org/texlive/windows.html#tlaunch Jürgen > > Riki > signature.asc Description: This is a digitally signed message part
Re: Windows Installers: TESTING ONLY
Am Dienstag, den 15.05.2018, 23:33 -0400 schrieb Richard Kimberly Heck: > I have finally managed to build Windows installers for 2.3.0. Just for the records, your efforts to get this back on track are highly appreciated. I hope we can sort out the remaining problems. Jürgen signature.asc Description: This is a digitally signed message part
Re: Windows Installers: TESTING ONLY
Richard Kimberly Heck wrote: > > 1. When starting LyX, a command window is presented and retained. > > Closing the command window closes LyX. > > I saw this, too, on Windows 10, but did not know it was unusual. I did > not change anything in the installer that should have affected this. IIRC there used to be whole routine hidden somewhere in nsi scripts to take care of hiding the console (our app is launched as a console one). Don't know how much up-to-date this info is... Pavel
Re: Windows Installers: TESTING ONLY
On 05/16/2018 12:58 AM, Andrew Parsloe wrote: > On 16/05/2018 3:33 p.m., Richard Kimberly Heck wrote: >> I have finally managed to build Windows installers for 2.3.0. They can >> be found here: >> >> http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ >> >> Let me emphasize again that >> >> THESE ARE FOR TESTING ONLY >> >> I have tested them a little bit myself, but not a whole lot. They seem >> to work, basically---I compiled the tutorial---but that's as far as I'm >> going to go in vouching for them. My understanding of the installer code >> is pretty basic at this point. >> >> The executables were cross-compiled using MinGW on Linux. So these are >> not at all the same binaries that we have previously been distributing. >> The installers themselves, however, are pretty much the same, though >> without the "Update MiKTeX" code, which has just been commented out. If >> we want to include it, but issue some kind of warning, then I think that >> will need to be translated. I know where to put the translated strings, >> but I'm not entirely sure how to get them from the translators, and that >> will of course take time. >> >> Longer term, I have some thoughts about how to improve our situation on >> Windows, and there's been vigorous discussion over on the user list. But >> I'll save that for after we get an installer for 2.3.x. >> >> Riki >> >> PS Certainly one thing I've learned is that installing LyX with MikTeX >> takes *forever*, and I've got a fast internet connection. It would be >> nice to know what packages we need to install to compile the User Guide, >> etc, and just install those, rather than every single package LyX could >> possibly need. This is not trivial, since some of those are font >> definitions. > I uninstalled my current 2.3.0 (from Uwe's very first 2.3.0 installer, > which has worked perfectly for me) and tried the link above (not the > bundle). LyX installed, but there are problems on my windows 7 machine. > > 1. When starting LyX, a command window is presented and retained. > Closing the command window closes LyX. I saw this, too, on Windows 10, but did not know it was unusual. I did not change anything in the installer that should have affected this. > 2. LyX does not create a personal LyX2.3 directory. (It should be at > C:\Users\Andrew\AppData\Roaming\LyX2.3 in my case.) When I made my > previous LyX2.3 directory available (from Uwe's installation), LyX > didn't recognize it and reconfiguring was no help. It looks like I made a slight mistake in configuring. The user directory is at \LyX, rather than \LyX2.3. I'll fix that. > 3. The Uninstall-LyX.exe program did not terminate. I had to close it > with the windows task manager. Just tried it, and it worked fine here. I think. I mean, it closed, but I'm far from sure that it actually uninstalled everything it had installed. Riki
Re: Windows Installers: TESTING ONLY
On 05/16/2018 08:22 AM, Pavel Sanda wrote: > Andrew Parsloe wrote: >> PS Re your PS and *forever*, that's one more reason for treating MiKTeX and >> LyX as distinct programs and not bundling them together. > Or we might consider using TeXLive as default instead of MikTeX if it works > better, now would be actually proper time to do it... > Bundle install with MikTeX produced installing time measured in hours > when I tried our installer couple weeks back. That is insane, but I do not > know whether we have real alternatives. The issue is that the basic MiKTeX install gives one very little. Not enough even to compile the Introduction, largely due to font metric files. > What install choices we have with TeXLive? Bundling 4gb of data is not an > option, but there might be small installer which can be conditioned on base > installation, without docs and we would be suddenly in the realm of 50-200mb. Yes, that would be the way to go, if we could do it. Riki
Re: Windows Installers: TESTING ONLY
Andrew Parsloe wrote: > PS Re your PS and *forever*, that's one more reason for treating MiKTeX and > LyX as distinct programs and not bundling them together. Or we might consider using TeXLive as default instead of MikTeX if it works better, now would be actually proper time to do it... Bundle install with MikTeX produced installing time measured in hours when I tried our installer couple weeks back. That is insane, but I do not know whether we have real alternatives. What install choices we have with TeXLive? Bundling 4gb of data is not an option, but there might be small installer which can be conditioned on base installation, without docs and we would be suddenly in the realm of 50-200mb. Bonus points would be fixed texlive version without on-the-fly updates and compatibility of LaTeX output with linux distros. Pavel
Re: Windows Installers: TESTING ONLY
On 16/05/2018 3:33 p.m., Richard Kimberly Heck wrote: I have finally managed to build Windows installers for 2.3.0. They can be found here: http://ftp.lyx.org/pub/lyx/devel/lyx-2.3/ Let me emphasize again that THESE ARE FOR TESTING ONLY I have tested them a little bit myself, but not a whole lot. They seem to work, basically---I compiled the tutorial---but that's as far as I'm going to go in vouching for them. My understanding of the installer code is pretty basic at this point. The executables were cross-compiled using MinGW on Linux. So these are not at all the same binaries that we have previously been distributing. The installers themselves, however, are pretty much the same, though without the "Update MiKTeX" code, which has just been commented out. If we want to include it, but issue some kind of warning, then I think that will need to be translated. I know where to put the translated strings, but I'm not entirely sure how to get them from the translators, and that will of course take time. Longer term, I have some thoughts about how to improve our situation on Windows, and there's been vigorous discussion over on the user list. But I'll save that for after we get an installer for 2.3.x. Riki PS Certainly one thing I've learned is that installing LyX with MikTeX takes *forever*, and I've got a fast internet connection. It would be nice to know what packages we need to install to compile the User Guide, etc, and just install those, rather than every single package LyX could possibly need. This is not trivial, since some of those are font definitions. I uninstalled my current 2.3.0 (from Uwe's very first 2.3.0 installer, which has worked perfectly for me) and tried the link above (not the bundle). LyX installed, but there are problems on my windows 7 machine. 1. When starting LyX, a command window is presented and retained. Closing the command window closes LyX. 2. LyX does not create a personal LyX2.3 directory. (It should be at C:\Users\Andrew\AppData\Roaming\LyX2.3 in my case.) When I made my previous LyX2.3 directory available (from Uwe's installation), LyX didn't recognize it and reconfiguring was no help. 3. The Uninstall-LyX.exe program did not terminate. I had to close it with the windows task manager. Andrew PS Re your PS and *forever*, that's one more reason for treating MiKTeX and LyX as distinct programs and not bundling them together. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
