Re: Problem with kpsewhich on a new instal

I should add that I am looking for a solution where TL would continue
to work after a move of directories  -- WITHOUT -- having to change anything
in TL, meaning, in a robust way.

Paulo Ney

On Mon, May 18, 2026 at 5:49 PM Paulo Ney de Souza <[email protected]>
wrote:

>
> On Mon, May 18, 2026 at 3:30 PM Karl Berry <[email protected]> wrote:
>
>> Paulo - sorry, I don't understand your problem, but did you solve it?
>>
>
> I have not solved it yet, one of the problems is that experimenting with
> one recipe or another takes hours.... I am on a machine where I cannot even
> moun and ISO image.
>
> What I want it to install  it on:
>
> /A/paulo/texlive/2026/
>
> and then move the entire tree to:
>
> /B/paulo/texlive/2026/
>
> and have everything work as it was. And I have not been able to achieve
> that.
>
>
> If not, tell me how to run the installer to reproduce it.
>>
>
> The first thing I tried was to run the installer and enter
>
>       ~paulo
>
> and the installation directory.  That did not work.
> There is a small problem entering the tilda on the installer interface --
> you have to type it twice.
> But soon after you type it, it completed the whole like with the full
> path, and the installation
> proceeds to the end and does not work.
>
>
>
>> If NFS is involved, perhaps the problem is related to this:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1135783
>> although the error you're getting ("No such file or directory")
>> is different than the errors there.
>>
>
> No, it is not that.
>
> You cannot even run "kpsewhich --var-value TEXMFLOCAL".  It lloks like
> it is using arg[0] to locate itself and then, it fails, and the
> installation does
> not work.
>
> It was suggested here to use $HOME, but the installer would not accept
> that. This time it tells you it is not accepting.
>
> I am trying to understand what the "portable" option really does..
>
> Pauulo Ney
>
>