The official Solus repository provides only texlive-base (current version: 20160523b-6) for installation. How can one install texlive-full (current version: 2016) on Solus Linux?
4 Answers
texlive-full installation
The following provides a step-by-step guide for installing texlive-full on Solus Linux. Plase see this texlive-full quick install for detailed instructions.
There are a number of ways to install texlive-full like network install, iso install, etc. A more detailed description can be found in above link. Assuming network install, the first step is to download the installer and run the install-tl script.
After the installation is done, the next step is setup the PATH variable. Add the following two lines to your bashrc file located in your home directory. Full path of the bashrc file is: /home/username/.bashrc.
PATH=/usr/local/texlive/2016/bin/x86_64-linux:$PATH
export PATH
Note
- Please do not set the
PATHvariable asPATH=$PATH:/usr/local/texlive/2016/bin/x86_64-linux. The reason for this will be explained later. - Choose the syntax appropriate for your shell, your installation directory, and your platform for setting up the
PATHvariable. For example if you have a 32-bit platform usePATH=/usr/local/texlive/2016/bin/i386-linux:$PATH
Next, logout and then after login check if the the PATH variable is properly set or not, run this command: echo $PATH. This should output something similar to:
/usr/local/texlive/2016/bin/x86_64-linux:/usr/local/bin:/usr/bin:/bin
This is it, check if latex is properly installed by running the command latex. This should output something like:
This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016) (preloaded format=latex)
restricted \write18 enabled.
**
Setting up TeXstudio in Solus linux
The above was the easy part. Most of us work with an integrated editor such as TeXstudio when working with latex. The following guide shows how to setup an editor such as TeXstudio to work with texlive-full in Solus linux. Although the following is written for TeXstudio in mind, it should work with other editors also with appropriate changes.
Install TeXstudio from the software center. The problem is that this will also install the texlive-base package present in the Solus repository. The reason is that TeXstudio depends upon the texlive-base package and the Solus software center does not recognize the texlive-full installation that is already installed on the system (if you followed the guide till now, that is). I couldn't find a workaround this. No worries though, proceed with the installation of both TeXstudio and texlive-base package.
After the install is done, you would have two different versions of texlive installed on the system.
texlive-fullwhich was installed manually.texlive-basewhich was installed along withTeXstudio.
Now, if you compile a latex document via the terminal it will compile via the texlive-full package. (Hence the reason for setting up the PATH variable as PATH=/usr/local/texlive/2016/bin/x86_64-linux:$PATH). But if you compile your document using TeXstudio, then it will compile via the texlive-base package.
Hence, the next step is to manually configure TeXstudio to use the texlive-full package.
- Open
TeXstudioand go toOptions -> Configure TeXstudio -> Commands - There you will see the different programs available in the
texlivepackage. - Click on the
Select Programicon on the right side of the pane, and browse to thetexlive-fullinstallation directory. in my case, this is :/usr/local/texlive/2016/bin/x86_64-linux/. Find and select the appropriate program for each of:latex, pdflatex, xelatex, lualatexand you are done
That's it !!!
- 51
-
1This should not be necessary. Where exactly was that path change made? In Ubuntu for example (I don't know solus), you can add it to your location dot-profile or the global version /etc/profile. Logout and in again for it to be effective. A lot of users add the path change to dot-bashrc, which does not affect texstudio when texstudio is started via a menu or doubleclicking a tex file. Then you do not need full paths for stuff in the texstudio configuration.. This is a very common error on Linux when setting up texlive. – daleif Jan 15 '17 at 07:48
-
@daleif you are absolutely right that path change done in
.profiledoesn't affect TeXstudio. For TeXstudio to use thetexlive-fullpackage instead of thetexlive-basepackage we need to configure TeXstudio manually. This explained in the second part of the guide. The path change is done is so that thattexlive-fullpackage is used when someone doesn't want to compile a latex document via the command line without the need for a text editor like TeXstudio. – Orion Jan 16 '17 at 13:39 -
It should be the other way round. Things in
.bashrcshould not affect texstudio if texstudio is loaded via a menu or similar. If configured correctly, it should not be necessary to manually set those paths in TeXStudio. A normal naïve user will not know how to do that (they don't know where LaTeX is), it should be enough to have the correct paths set up. Exactly what is Solus Linux? – daleif Jan 16 '17 at 13:53 -
@daleif I'm confused here! You agree with me that changes made in the
PATHvariable in.bashrcor.profiledo not affect editors likeTeXstudioright? – Orion Jan 16 '17 at 14:00 -
No, changes to
.profileshould work, it does on Ubuntu, but you have to log out and in again for changes to do anything..profile(again on Ubuntu) is only read at login. I've tried to install Solus Linux in a VM, but is unable. – daleif Jan 16 '17 at 14:10 -
@daleif why? whats the issue? I myself am using Solus (Solus 2017.01.01.0 64-bit) in VM (Virtualbox 5.1.12) – Orion Jan 16 '17 at 15:37
-
no idea, whenever I try to log in to the live ISO, it immediately logs be out again. Perhaps my VirtualBox is too old. – daleif Jan 16 '17 at 15:49
-
Also, you can install TeXStudio without texlive-base, just install it without the recommended stuff (it is not a requirement). On Ubuntu it is
sudo apt-get install texstudio --no-install-recommends– daleif Jan 16 '17 at 15:56 -
It is best to create a dummy package which provides
texlive-base(and whatever else) so that your package manager does not insist on installing another TeX distribution. While it is possible to manage this situation, it is the source of considerable problems, mysterious errors and great confusion. That is, it is not recommended at all. – cfr Jan 16 '17 at 22:32 -
FWIW, I add the path change in
/etc/profile.d/cfr_texlive.shunless the current user isroot, in which case I do nothing. But this kind of thing varies by distro. What you should not need to do is to edit the settings for every editor manually. Also, you should not need to actually installtexlive-base. – cfr Jan 16 '17 at 22:36 -
BTW: just noticed that TeXStudio 2.12 does not find any LaTeX at all or at least leave the Tools/Commands list empty. TS 2.11 fills in Tools/Commands just fine. And if one installs TS 2.12 after purgin TS 2.11 the local TS configuration stays on an TS 2.12 works fine (at least on my Ubuntu 14.04) – daleif Jan 20 '17 at 11:28
The full installation of TeX Live is available in Solus. It contains the full content of the 1.9GB texlive-20160523b-texmf.tar.xz (minus docs)
Installing these packages would result in the full TeX Live install.
eopkg list-available | grep texlive
I am in the process of creating a TeX Live meta package so that you can install the complete TeX Live more conveniently by installing the texlive-all package. This will be available sometime in the next few days.
- 21
-
-
@sunnyflunk The package that you mentioned is not the full texlive package. It does not contain many packages and my Latex document fails to compile with it stating that packages are missing. Moreover I don't think that
texlive-fullpackage is only 1.9GB, the official texlive-full-2016 iso is of 3.1GB. – Orion Jan 18 '17 at 12:16 -
@Orion The reason the iso is larger as it contains 16 copies of the same packages in different binary formats. Are you able to provide a sample doc to me via the forums as I'd like to resolve any issue people experience with TeX Live – sunnyflunk Jan 19 '17 at 00:39
You can simply install TexStudio without installing TeX Live from the Solus repositories.
Once you've installed TeX Live (the install script from the TeX Live homepage works fine), install the dependencies of TexStudio except TexLive using eopkg:
sudo eopkg it zlib poppler-qt5 qt5-base qt5-script libx11 libstdc++ zlib poppler-qt5 qt5-base qt5-script libx11 libstdc++
Then install TexStudio without dependencies:
sudo eopkg it --ignore-dependency texstudio
Since you've already manually installed the needed dependencies, the only thing that won't be installed is texlive-base.
You'll still have to fix the PATH as mentioned by Orion, and you still have to manually set the various command properties in the TexStudio settings, but you won't have two competing TeX Live installations on your system.
- 11
This is just a comment, a bit too long.
Have I understood you right:
- You manually installed upstream texlive? Where was it installed? If my memory is correct it installs in /usr/local/texlive/2016 by default.
- Did you ask it to make soft lines in common places? (not recommended)
- You installed texstudio which in addition also installed texlive-base presumably from Debian (not because texstudio needs it, but because it us listed as recommended)
Is this correct?
Thus you now have two latex installations. And we need to use the right one.
As mentioned I'm not familiar with solus Linux, and for some reason it does not like my version of virtualbox, so I cannot test it.
Under Ubuntu it is enough to add the path change to dot-profile (adding it also to dot-bashrc does not hurt, but it alone is often not enough). But this being a different Linux, we do not know if dot-profile or dot-bashrc is even being used.
- 54,450
-
@Orion I give up trying to help on this issue. I cannot get it to work on my home laptop either, though I could install it, it will not let me log in (presumably an X crash). From the forums one an read that this is not an OS designed to be used in a virtual setting, so much for testing. We will need a fix env in order to test texstudio. – daleif Jan 17 '17 at 16:44
-
eopkg. This in turn implies that either you can install packages listed in the official repo or you build it from source! – Orion Jan 16 '17 at 14:38pacman,dnf,eopkgor whatever. The principle is the same regardless. – cfr Jan 16 '17 at 20:23