Hi, just testing a module on a fresh Linux (Debian 6.0.5-i386) with the latest standalone. No messages when calling 'setuptex', but the PATH to the binaries is not set correctly here. I manually added the binary path to '.bashrc' and it worked. # add ConTeXt binaries to PATH PATH=~/context/tex/texmf-linux/bin:$PATH Peter
On 24-8-2012 17:13, Peter Rolf wrote:
Hi,
just testing a module on a fresh Linux (Debian 6.0.5-i386) with the latest standalone. No messages when calling 'setuptex', but the PATH to the binaries is not set correctly here. I manually added the binary path to '.bashrc' and it worked.
# add ConTeXt binaries to PATH PATH=~/context/tex/texmf-linux/bin:$PATH
recently i had to configure a debian machine (normally i use opensuse) and found out that some scripts didn't work because instead of bash something dash (b->d) was used ... maybe that's the issue Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 08/24/2012 11:36 AM, Hans Hagen wrote:
recently i had to configure a debian machine (normally i use opensuse) and found out that some scripts didn't work because instead of bash something dash (b->d) was used ... maybe that's the issue
The "safest" thing to do for scripts is to stick to /bin/sh - the POSIX shell. Bash is a good shell but not the default shell on many *nix, BSD and *nux systems. On BSD, it has to be installed as an optional package. /bin/sh may not always be the default but I've yet to find a system where it isn't present in the default install. /bin/sh is a superset of the original Unix Bourne shell and implements most features of ksh - the Korn shell. Relying on the features of any other shell (bash, dash, csh, zsh &c.) may get some extra functionality but breaks portability. Bash will run scripts written for /bin/sh without modification but the reverse is not always true. Just an FYI from someone who's been using Unix, derivatives and work-alikes since Bell Labs V7 :) -- Bill Meahan Westland, Michigan USA
On Fri, 24 Aug 2012, Peter Rolf wrote:
Hi,
just testing a module on a fresh Linux (Debian 6.0.5-i386) with the latest standalone. No messages when calling 'setuptex', but the PATH to the binaries is not set correctly here. I manually added the binary path to '.bashrc' and it worked.
# add ConTeXt binaries to PATH PATH=~/context/tex/texmf-linux/bin:$PATH
In the archlinux PKGBUILD that I maintain, I use the following setuptex: ~~~ TEXMFOS=/opt/context-minimals/texmf-linux export TEXMFOS TEXMFCACHE=$HOME/texmf-cache export TEXMFCACHE unset TEXINPUTS MPINPUTS MFINPUTS PATH=$TEXMFOS/bin:$PATH export PATH OSFONTDIR="$HOME/.fonts;/usr/share/fonts;" export OSFONTDIR ~~~ Aditya
On Fri, Aug 24, 2012 at 5:13 PM, Peter Rolf
Hi,
just testing a module on a fresh Linux (Debian 6.0.5-i386) with the latest standalone. No messages when calling 'setuptex', but the PATH to the binaries is not set correctly here. I manually added the binary path to '.bashrc' and it worked.
# add ConTeXt binaries to PATH PATH=~/context/tex/texmf-linux/bin:$PATH
You should call $> . setuptex (warning: there is an initial '.' ! ) or $>source setuptext but the last one is a bash extension. -- luigi
On 08/24/2012 12:32 PM, luigi scarso wrote:
$>source setuptext but the last one is a bash extension.
Actually it is in ksh (or ksh93) predefined as an alias for '.' I *think* it's in the POSIX standard but I'm not quite sure. 'sh' on Debian-derived systems (including *buntu) is an alias for dash, not the POSIX shell although the man page for dash says it is being worked on for POSIX compliance. -- Bill Meahan Westland, Michigan USA
participants (5)
-
Aditya Mahajan -
Bill Meahan -
Hans Hagen -
luigi scarso -
Peter Rolf