[SOLVED] Installation of texlive from iso

pocker · 03-22-2022, 06:46 AM

Hello.

Since the texlive package provided by a full installation of slackware64 15.0 is not complete, I removed it.

I downloaded the .iso install from tug.org and the installation was successful. Except for one little thing.

One of the last things to do is to add this:

Code:

MANPATH=/usr/local/texlive/2021/texmf-dist/doc/man:$MANPATH; export MANPATH
INFOPATH=/usr/local/texlive/2021/texmf-dist/doc/info:$INFOPATH; export INFOPATH
PATH=/usr/local/texlive/2021/bin/x86_64-linux:$PATH; export PATH

and I want this to be system-wide. I added these 3 lines to the end of /etc/profile

When I open a terminal with a regular user, everything is fine, i.e., all latex files (executables, formats, etc) are found:

Code:

$ which latex
/usr/local/texlive/2021/bin/x86_64-linux/latex

Also,

Code:

$ su -
# which latex
/usr/local/texlive/2021/bin/x86_64-linux/latex

BUT

Code:

$ su
# which latex
which: no latex in (/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin)

Why "su -" finds the correct path and "su" not? Is /etc/profile the correct place to add those 3 lines?

Kind regards

dhalliwe · 03-22-2022, 09:58 AM

In the man page for 'which', I get:

Quote:

Which takes one or more arguments. For each of its arguments it prints to stdout the full
path of the executables that would have been executed when this argument had been entered
at the shell prompt. It does this by searching for an executable or script in the directo‐
ries listed in the environment variable PATH using the same algorithm as bash(1).

So I would suspect that you have different $PATH specifications. Try 'echo $PATH' before each 'which" call.

After doing "su', I get

Quote:

/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin

....but after doing "su -', I get

Quote:

/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/java/bin:/usr/lib64/java/jre/bin:/usr/lib64/java/bin:/usr/lib64/libexec/kf5:/usr/lib64/kde4/libexec:/usr/lib64/qt5/bin

...on my system (recent upgrade from 14.2 to 15.0) from a terminal window in XFCE.

pocker · 03-22-2022, 02:30 PM

The su's manual says that

Code:

-, -l, --login
           Provide an environment similar to what the user would expect had
           the user logged in directly.

           When - is used, it must be specified before any username. For
           portability it is recommended to use it as last option, before any
           username. The other forms (-l and --login) do not have this
           restriction.

this explain why I get this:

Code:

$ su
# echo $PATH
/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin

and this

Code:

$ su -
# echo $PATH
/usr/local/texlive/2021/bin/x86_64-linux:/usr/local/sbin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/games:/usr/lib64/libexec/kf5:/usr/lib64/qt5/bin

Sure, I can create an alias as "su = 'su -'". But, is there any file that I can change in order to "su" to have the same $PATH as "su -" ?

Kind regards

JayByrd · 03-22-2022, 02:55 PM

In that same man page for su, it states that when not using "su -" (which is the same as "su --login"):

Code:

Note that the default behavior for the environment is the following:

        The $HOME, $SHELL, $USER, $LOGNAME, $PATH, and $IFS environment variables
               are reset.

        If --login is not used, the environment is copied, except for the variables
               above.

It also says exactly what these environment variables are reset to:

Code:

$PATH
        reset according to the /etc/login.defs options ENV_PATH or ENV_SUPATH ...

I have checked the defaults in Slackware's "/etc/login.defs" file, and they indeed match the PATH output that you posted in the OP for "su":

Quote:

/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin

pocker · 03-22-2022, 03:49 PM

Quote:

Originally Posted by JayByrd

In that same man page for su, it states that when not using "su -" (which is the same as "su --login"):

It also says exactly what these environment variables are reset to:

Code:

$PATH
        reset according to the /etc/login.defs options ENV_PATH or ENV_SUPATH ...

I have checked the defaults in Slackware's "/etc/login.defs" file, and they indeed match the PATH output that you posted in the OP for "su":

There is only one thing that comes to my mind: RTFM (I'm saying this to me......... )

Anyway, Thanks !!

franzen · 03-23-2022, 01:57 AM

Quote:

Originally Posted by pocker

Since the texlive package provided by a full installation of slackware64 15.0 is not complete, I removed it.

Glad your issue was solved, another option would have been to install texlive-extra and texlive-docs from SBo to have a complete texlive installation.
I'd like to know if you just didn't know about that, or if there are other reasons to prefer the iso-installation.

pocker · 03-23-2022, 06:15 AM

Quote:

Originally Posted by franzen

Glad your issue was solved, another option would have been to install texlive-extra and texlive-docs from SBo to have a complete texlive installation.
I'd like to know if you just didn't know about that, or if there are other reasons to prefer the iso-installation.

Before installing Slackware 15.0 I was using Devuan (and I always installed texlive-full to avoid any missing package/feature). Last year one of my students (I'm a professor) sent to me a PDF that was different of what I was expecting (the font on the pdf was different when compiled on my machine). After several days trying to figure out what was happening, I realized that one package, more precisely the 'ae' package, changed from texlive 2019 to 2020 (or from 2020 to 2021, not sure about the year). Am I sure that is the 'ae' package? Yes....
So, I decided to install texlive 2021 on Devuan, and voilá!! Using/not using the 'ae' package was giving me different font on the generated PDF.

Also, I realized that installing from iso it is possible to have a up-to-date texlive installation (although this is not a big deal).

WHen I installed Slackware 15, I just started using the provided texlive package (and the SBo for 15.0 wasn't ready yet ... but now they are).
Compiling one document with the provided texlive was giving me wrong font (not fault of 'ae' package this time) on the PDF.
The easiest solution to me was to install from iso, since I already have (almost)all step-by-step to do it.

The curiosity about "su" and "su -" was just a small thing since I'm the only one that uses the computer.

That's it, hope to answered your question.

Kind regards

franzen · 03-23-2022, 07:00 AM

Quote:

Originally Posted by pocker

That's it, hope to answered your question.

Yes, thanks. If you ever install eveything from 15.0+SBo and something behaves strange, let me know.