startup script stubs (for unix)

startup script stubs (for unix)

[frantisek holop]

hello gang,

after almost a year of traveling i am back.
anybody missed me? :]  thought so.

i have made the openbsd installation of context
on top of texexec3 wiki page on the context wiki
because i frequently reinstall my notebook and start
from scratch with all my software.  i realize by now
texlive is the new thing but before i make context
minimal work on openbsd i still prefer to bring
up to date context  on the much less bloated base
of tetex3.

my biggest gripe at the moment always at the end
the ruby scripts...

but this is something that could be easily changed.
i personally find the following instructions the
most helpful:
http://wiki.contextgarden.net/TeTeX_3.0_installation#Ruby_scripts

at the moment, the directory
/usr/local/share/texmf-local/scripts/context/stubs/unix/
contains a bunch of scripts that are nice but unusable because

1. they dont have the x bit set

2. most of them contain something like

	texmfstart somescript "$@"

while texmfstart itself is not defined anywhere

it would be really nice if these stubs could be just dropped
as replacements for any current scripts and work out of the box.

i am not sure my proposed solution is a good one, because
frankly, except texexec i have never used any of the other
scripts..  but looking at the afore-quoted wikipage it seems
to me that the author favoured the approach of calling all
the other sripts using texexec.  the beauty of this is
that no other scripts need to be installed.

so what do you people think about the following approach:

stub for texmfstart to be put under /usr/local/bin/texmfstart:
#!/bin/sh

ruby `kpsewhich --format=texmfscripts texmfstart.rb` "$@"

stub for texexe to be put under /usr/local/bin/texexec:
#!/bin/sh

SCRIPTNAME=`basename $0`

if [ X"$SCRIPTNAME" = X"texexec" ]; then
        exec texmfstart texexec.rb "$@"
else
        exec texmfstart $SCRIPTNAME "$@"
fi

and all the other script stubs could be removed i guess...

-f
-- 
good words cost no more than bad.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: startup script stubs (for unix)

[Mojca Miklavec]

On Wed, Feb 11, 2009 at 12:20 AM, frantisek holop wrote:
> hello gang,
>
> after almost a year of traveling i am back.
> anybody missed me? :]  thought so.

Hello Frantisek,

Just a quick note ... not too many people on the list might be able to
follow since there are probably not too many tetex3 users around, and
the page you refer to is old as earth, so keep using whatever fits you
best. Did you want to suggest changes on the webpage or did you want
to ask if some procedure works?

(I fully understand why you want to keep using tetex.)

> i have made the openbsd installation of context
> on top of texexec3 wiki page on the context wiki
> because i frequently reinstall my notebook and start
> from scratch with all my software.  i realize by now
> texlive is the new thing but before i make context
> minimal work on openbsd i still prefer to bring
> up to date context  on the much less bloated base
> of tetex3.
>
> my biggest gripe at the moment always at the end
> the ruby scripts...
>
> but this is something that could be easily changed.
> i personally find the following instructions the
> most helpful:
> http://wiki.contextgarden.net/TeTeX_3.0_installation#Ruby_scripts
>
> at the moment, the directory
> /usr/local/share/texmf-local/scripts/context/stubs/unix/
> contains a bunch of scripts that are nice but unusable because
>
> 1. they dont have the x bit set
>
> 2. most of them contain something like
>
>        texmfstart somescript "$@"
>
> while texmfstart itself is not defined anywhere

That folder is not meant to be a replacement for binaries. It's just a
folder where files can be taken from and put somewhere else
afterwards. They don't have the x bit set because zip on windows
doesn't handle permission bits.

Concerning texmfstart: it's now part of texlive and it's part of
minimals. You cannot expect recent binaries to be already part of an
ancient tex distribution. Hans probably won't add texmfstart to that
folder since distribution is supposed to take care of that.

If you need a simple command to fetch all in one run, just do (single
line in case it gets broken):
   rsync -av rsync://contextgarden.net/minimals/current/bin/context/linux/bin/
/usr/local/bin/

> it would be really nice if these stubs could be just dropped
> as replacements for any current scripts and work out of the box.

Is there any other problem apart from the executable bit (that Hans is
not able to fix comfortably)?

> i am not sure my proposed solution is a good one, because
> frankly, except texexec i have never used any of the other
> scripts..  but looking at the afore-quoted wikipage it seems
> to me that the author favoured the approach of calling all
> the other sripts using texexec.

You mean texmfstart?

>  the beauty of this is
> that no other scripts need to be installed.
>
> so what do you people think about the following approach:
>
> stub for texmfstart to be put under /usr/local/bin/texmfstart:
> #!/bin/sh
>
> ruby `kpsewhich --format=texmfscripts texmfstart.rb` "$@"

At the moment this file is a literal copy of texmfstart.rb. It's like
a chicken-and-egg problem. Hans wants to get rid of kpathsea, but by
copying the file one doesn't always get the latest texmfstart (one
needs to make sure that it's always up-to-date). The "ruby `kpsewhich
..." approach is also OK.

> stub for texexe to be put under /usr/local/bin/texexec:
> #!/bin/sh
>
> SCRIPTNAME=`basename $0`
>
> if [ X"$SCRIPTNAME" = X"texexec" ]; then
>        exec texmfstart texexec.rb "$@"
> else
>        exec texmfstart $SCRIPTNAME "$@"
> fi
>
> and all the other script stubs could be removed i guess...

You don't need to copy other files/stubs if you don't need them, but
some people depend on existence of some tools like ctxtools (which is
easier to use than texmfstart ctxtools). If you don't need other
scripts, just ignore them.

(The scripts described on tetex installation page are probably not
used my many people. But those pages need to be fixed and unified
somehow.)

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: startup script stubs (for unix)

[Peter Münster]

On Wed, 11 Feb 2009, frantisek holop wrote:

> i have made the openbsd installation of context
> on top of texexec3 wiki page on the context wiki
> because i frequently reinstall my notebook and start
> from scratch with all my software.  i realize by now
> texlive is the new thing but before i make context
> minimal work on openbsd i still prefer to bring
> up to date context  on the much less bloated base
> of tetex3.

Hello,

teTeX3 is less bloated than ConTeXt minimals??

I suggest 2 options:

1.) Install cont-tmf.zip and fonts on top of tetex3
    For this option, you can take a look into
http://pmrb.free.fr/texlive/src/ where you can find texlive.spec. The ideas
in this file should also work for tetex (the name of this file was
tetex.spec some time ago).

2.) Install context-minimals beside tetex3
    Since I have no more time to maintain tetex or texlive spec files, I
use this option (only with texlive instead of tetex). All my context stuff
is now in /opt/context and updated according to
http://wiki.contextgarden.net/ConTeXt_Minimals
Perhaps there are no openbsd binaries in this distribution, but it should
be easy to add support for openbsd in
http://svn.contextgarden.net/minimals-src/build-binaries/build-binaries.sh

Cheers, Peter

-- 
Contact information: http://pmrb.free.fr/contact/

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: startup script stubs (for unix)

[frantisek holop]

hmm, on Fri, Feb 13, 2009 at 07:17:34PM +0100, Peter Münster said that
> On Wed, 11 Feb 2009, frantisek holop wrote:
> 
> > i have made the openbsd installation of context
> > on top of texexec3 wiki page on the context wiki
> > because i frequently reinstall my notebook and start
> > from scratch with all my software.  i realize by now
> > texlive is the new thing but before i make context
> > minimal work on openbsd i still prefer to bring
> > up to date context  on the much less bloated base
> > of tetex3.
> 
> Hello,
> 
> teTeX3 is less bloated than ConTeXt minimals??

no :]  read it again.
tetex3 is less bloated than texlive, not context minimals.

> Perhaps there are no openbsd binaries in this distribution, but it should
> be easy to add support for openbsd in
> http://svn.contextgarden.net/minimals-src/build-binaries/build-binaries.sh

yes, this is where i am headed in the long run.
native context minimals on openbsd.

-f
-- 
oh no, not deja-vu again.  oh no, not deja-vu again.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: startup script stubs (for unix)

[frantisek holop]

hmm, on Fri, Feb 13, 2009 at 04:52:49PM +0100, Mojca Miklavec said that
> That folder is not meant to be a replacement for binaries. It's just a
> folder where files can be taken from and put somewhere else
> afterwards. They don't have the x bit set because zip on windows
> doesn't handle permission bits.

ok, i have a lot of catching up to do because of the enormous
volume of mail hitting this list, but let me ask this.  all i want
is a simple alias/shell_script/stub/whatever to run context on
a .tex file.  that's all.  as someone coming from latex (a long time
ago) and running commands like "latex doc.tex" or "pdflatex doc.tex"
i always expected that to be "context doc.tex".  when i started using
context, it was "texexec doc.tex".

as a user i don't mind what's in the background, perl, shell, ruby
or a bone fide binary, all i'd like to do is have an official
(as opposed to hand rolled/home made) context command that runs
everything that is needed to process the .tex file.

is there something like that? if not, will be? :]

-f
-- 
the 4th world war will be fought with sticks and rocks.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

Re: startup script stubs (for unix)

[Mojca Miklavec]

On Fri, Feb 13, 2009 at 7:40 PM, frantisek holop <minusf@obiit.org> wrote:
> hmm, on Fri, Feb 13, 2009 at 04:52:49PM +0100, Mojca Miklavec said that
>> That folder is not meant to be a replacement for binaries. It's just a
>> folder where files can be taken from and put somewhere else
>> afterwards. They don't have the x bit set because zip on windows
>> doesn't handle permission bits.
>
> ok, i have a lot of catching up to do because of the enormous
> volume of mail hitting this list, but let me ask this.  all i want
> is a simple alias/shell_script/stub/whatever to run context on
> a .tex file.  that's all.  as someone coming from latex (a long time
> ago) and running commands like "latex doc.tex" or "pdflatex doc.tex"
> i always expected that to be "context doc.tex".  when i started using
> context, it was "texexec doc.tex".
>
> as a user i don't mind what's in the background, perl, shell, ruby
> or a bone fide binary, all i'd like to do is have an official
> (as opposed to hand rolled/home made) context command that runs
> everything that is needed to process the .tex file.

That's texexec and it's official on any TeX distribution, the only
problem is that it doesn't work so well in older distributions. Any
recent distribution has a properly working texexec command.

But if you want to fiddle with home-made distribution, you need to be
ready for using home-made solutions. That's all.

There is also a more recent command "context" which uses luatex engine
in the background. But I would not recommend you to try to enable it
on the ancient distribution until you figure out all the other bits
and pieces. You need to configure way too many files ... and you
probably don't want to do every time when you reinstall the system if
you do that often. It's much easier to install the minimals.

> is there something like that? if not, will be? :]

Sure, there is - as explained above. It's just that nobody cares about
tetex any more and nobody will provide support for tetex. But if you
like it (for a reason - LaTeX hardly changes if you don't use XeTeX,
TikZ etc.) it's perfectly fine if you configure it to use the most
recent ConTeXt.

Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________