Setting .bash_profile settings on Ubuntu 18.04

Faki · 04-27-2022, 10:54 AM

Have made ~/.bash_profile in my home directory, that calls the file linge-profile.rc.

Here is the contents of ~/.bash_profile

Code:

gun_path="${HOME}/Opstk/bin/gun-1.0"
source ${gun_path}/linge/linge-profile.rc

And the contents of linge-profile.rc being

Code:

#!/bin/bash

linge-texlive-paths ()
{
  local -r tldir="${HOME}/Opstk/bld/texlive/2022"
  PATH=${tldir}/bin/x86_64-linux:${PATH}
  MANPATH=${tldir}/texmf-dist/doc/man:${MANPATH}
  INFOPATH=${tldir}/texmf-dist/doc/info:${INFOPATH}

  export PATH
  export MANPATH
  export INFOPATH
}

linge-texlive-paths

But, when I do echo $PATH, the directory ${tldir}/bin/x86_64-linux is not there. I also have a .profile. I am using Ubuntu 18.04.

TB0ne · 04-27-2022, 10:59 AM

Quote:

Originally Posted by Faki

Have made ~/.bash_profile in my home directory, that calls the file linge-profile.rc. Here is the contents of ~/.bash_profile

Code:

gun_path="${HOME}/Opstk/bin/gun-1.0"
source ${gun_path}/linge/linge-profile.rc

And the contents of linge-profile.rc being

Code:

#!/bin/bash
linge-texlive-paths ()
{
  local -r tldir="${HOME}/Opstk/bld/texlive/2022"
  PATH=${tldir}/bin/x86_64-linux:${PATH}
  MANPATH=${tldir}/texmf-dist/doc/man:${MANPATH}
  INFOPATH=${tldir}/texmf-dist/doc/info:${INFOPATH}

  export PATH
  export MANPATH
  export INFOPATH
}
linge-texlive-paths

But, when I do echo $PATH, the directory ${tldir}/bin/x86_64-linux is not there. I also have a .profile. I am using Ubuntu 18.04.

Why can't you just edit your PATH statement in ONE of your files, or add those statements there? Why source a separate file??

Faki · 04-27-2022, 12:48 PM

Because I am working on a user setup repository, such that user settings are not scattered all over the place.

TB0ne · 04-27-2022, 12:58 PM

Quote:

Originally Posted by Faki

Because I am working on a user setup repository, such that user settings are not scattered all over the place.

So you've got a .bash_profile, a .profile, .bashrc, and an linge-profile.rc....but don't want things 'scattered all over the place'?? They already ARE scattered.

Set things up in the default profile on your system, so any new users get the path info, by putting it in /etc/skel/.profile (or .bashrc). Edit your profile to have those variables, and you're done.

Faki · 04-27-2022, 01:05 PM

.profile and .bashrc were there already. Things are scattered, but not the actual commands (all are in directory ${HOME}/Opstk/bin/gun-1.0/linge). I just access them.

Faki · 04-27-2022, 01:07 PM

@TBOne What would you suggest as a good system? Remove .bash_profile and put things in the .bashrc? Have read that .bash_profile is intended for terminal prompt settings.

TB0ne · 04-27-2022, 01:55 PM

Quote:

Originally Posted by Faki

@TBOne What would you suggest as a good system? Remove .bash_profile and put things in the .bashrc? Have read that .bash_profile is intended for terminal prompt settings.

You were given this advice earlier; you then opened another thread for the same thing. Reported as duplicate.

Faki · 04-27-2022, 02:00 PM

With which one should we continue?

Faki · 04-27-2022, 02:02 PM

The other was about a problem as I could not see PATH being updated from ~/.bash_profile.

ondoho · 04-28-2022, 01:38 AM

Quote:

Originally Posted by Faki

Have made ~/.bash_profile in my home directory, that calls the file linge-profile.rc.

Here is the contents of ~/.bash_profile

Code:

gun_path="${HOME}/Opstk/bin/gun-1.0"
source ${gun_path}/linge/linge-profile.rc

And the contents of linge-profile.rc being

Code:

#!/bin/bash

linge-texlive-paths ()
{
  local -r tldir="${HOME}/Opstk/bld/texlive/2022"
  PATH=${tldir}/bin/x86_64-linux:${PATH}
  MANPATH=${tldir}/texmf-dist/doc/man:${MANPATH}
  INFOPATH=${tldir}/texmf-dist/doc/info:${INFOPATH}

  export PATH
  export MANPATH
  export INFOPATH
}

linge-texlive-paths

But, when I do echo $PATH, the directory ${tldir}/bin/x86_64-linux is not there. I also have a .profile. I am using Ubuntu 18.04.

Did you troubleshoot this at all? 'set -x'? Maybe remove the rather pointless enclosing function? Come to think of it, that might be the reason it's not working. Dunno. I did NOT troubleshoot your code.

pan64 · 04-28-2022, 02:15 AM

Quote:

Originally Posted by Faki

The other was about a problem as I could not see PATH being updated from ~/.bash_profile.

did you read your other thread about how and when those files are processed (~/.bash_profile and ~/.bashrc)