Re: [NTG-context] new debian context 2006.12.21-0.1
Norbert Preining [EMAIL PROTECTED] wrote: Hi all! New upstream, new debian package 2006.12.21-0.1 deb(-src) http://www.tug.org/texlive/Debian/ context/ Missing before I can upload (will upload) to Debian: - copyright file needs to be extended. I got the OK from Taco that everything but the cows fonts are GPLv2 or PD, those fonts I couldn't find for now, so it seems that it is ok. I have to write something up. Moreover, it's not acceptable for a Debian upload (and IMHO hardly acceptable for providing an archive for download) to mix in one archive GPL'ed and PD files, without clearly listing which is which. After all, PD means you can do anything, while the GPL is Copyleft, or in other words one of the most restrictive Open Source licenses. - Description: As Frank noted, something less commercial and more descriptive. And, in particular, something which explains in 5 lines why one would want to use ConTeXt instead of LaTeX. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] new debian context, upload to Debian
Taco Hoekwater [EMAIL PROTECTED] wrote: Everything in (the current versions of) cont-ext, cont-fmt and cont-img is either GPLv2 or Public Domain. Well, the interesting question is what is what? It's quite important to not handle a GPL'ed file as if it was Public Domain. Is there any chance to get a statement of them beign DFSG compatible? Otherwise I have to exclude some of it and put it into something like context-nonfree. BTW, as you are also one of the luatex people, same problem exists for luatex which I am also packaging. Please, please don't do that. The snapshots are bug-ridden and totally experimental. In this stage, we much prefer having only testers that know how to deal with unstable software. I have no opinion about this particular case, but if we only upload it to Debian experimental, we can expect its users to be able to deal with unstable and totally broken software. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Gerhard Kugler [EMAIL PROTECTED] wrote: On Mon, Oct 23, 2006 at 10:35:30AM +0200, Frank Küster wrote: or, if you have a bit experience, you can straight away add deb http://www.tug.org/texlive/Debian/ context/ to your /etc/apt/sources.list file and install context. After this, please tell us our experiences/failures/suggestions. Frank, is this truely a valid line for sources.list? Yes, I've got plenty of those. My apt shows errors with this line. which errors? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Taco Hoekwater [EMAIL PROTECTED] wrote:
Frank Küster wrote:
Can you point me to the place where it is documented which calls are
needed to be called
I was going to say: on the wiki, but that clearly wouldn't work
this time.
To actually update ConTeXt, assuming you already have a relatively
modern context installed, you say
# ctxtools --update
and that fetches the zip file(s) from the pragma site (or a mirror),
unpacks them, and updates the various perl and ruby scripts that come
with ConTeXt.
When this is done on a system where ConTeXt first came with a TeXlive or
teTeX installation, will this replace existing files, or will it put the
updated new files in TEMXFLOCAL or TEXMFHOME, respectively? Ah, I think
you have answered this already below.
You have to be root for this when you want to update the global install,
otherwise you have a few extra caveats, see below.
After a succesful update, you have to run
# texexec --make --all [--xetex | --aleph | --pdftex] formats
Where formats are the desired formats to run. The accepted list
at the moment is: the eight ConTeXt formats, in both long
(cont-en etc.) and short from (en,nl,de,it,fr,cz,
ro,uk), and mptopdf, and the metapost mems mpost and metafun.
So I guess this is the call that would also be needed if the update
itself goes via a package management, i.e. if one installs a new version
of the Debian ConTeXt package.
This works fine if you are root, and had a previous context update
done already. If you have not already and/or are not root, then you
have two big problems:
* TEXFORMATS as shipped with teTeX/TL is uncomplete: there is that
missing format-specific subdirectory.
So I guess TeXlive (and the existing teTeX packages within
Linux/BSD/... distributions) should do that, so that modern ConTeXt just
works.
If you are not root, then
you have to create a local texmf.cnf to overrule the default
texmf.cnf. I have:
TEXFORMATS= .;$TEXMF/web2c/{$engine,}
because context's texexec pushes the $engine setting to the
environment, this works fine (Originally this was supposed to
be handled by kpathsea, but like I said, that never got off
the ground)
It might be possible by setting, in texmf.cnf,
TEXFORMATS.xetex = .;$TEXMF/web2c{xetex,}
TEXFORMATS.pdftex = .;$TEXMF/web2c{pdftex,}
and so on. I'm not sure, however; this of course depends on which
progname ConTeXt uses (so it might need to be TEXFORMATS.cont-xetex or
whatever).
Not using texexec is not a big deal in itself, as long as you
restrict yourself to using pdfetex and know how to edit the
fmtutil config file, I guess. That's why you sometimes see that
approach promoted on the wiki.
I think, with the TEXFORMATS.$engine setup working, it should be
possible to use both, fmtutil and texexec, and get the same formats -
texexec might still be better in doing other update tasks.
* TEXFONTMAPS is also wrong: it makes pdftex (and dvipdfmx as well,
I guess) find the mapfiles for dvips before their own mapfiles
(those are shipped with ConTeXt).
This also sounds like a bug in TeXlive/teTeX.
* Lastly, ctxtools --update does a kpsewhich on context.tex to find
where to install the updated files. That only works if you have
write permission for that directory (i.e. you are root), or if you
have done a private install already.
So this means -update will always try to overwrite an existing
installation, and not automatically search for a writable directory
that's earlier in the TEXMF path? Even not as a fallback? This sounds
as if this tool could be improved.
I think that is all, but I may have missed something, so if you read
this message and know a thing or two about updating, please double
check my text. Thanks in advance.
I think it does help a lot, and we can work from there, testing with the
Debian ConTeXt package.
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
behind tds and web2c was that platforms could share trees, which is what i like: i have one set of trees for running all platforms (so, texmf-local it is here) That's not so much of a problem in Debian, because the package managment system will respect your changes and always keep texmf-local if you like. But generally I agree that this is suboptimal. AFAIK only the search path for texmf.cnf is hard-coded, and that can't be avoided. On the other hand, no one ever approached me and requested a relocation: What would you want, and in which cases? i think that there are a few more paths in there (you sometimes see them in var expansions, but normally they don't hurt) ; life would be easier if texmfcnf was always taken from an env var; actually, i set all important env vars anyway, if only because it isolates tex distrubutions (after all we're talking about a only a few vars than determins all); I trust you to do it right, but we've had a couple of bogus bugreports from people who set env vars wrongly, or completely forgot they ever had... I'll see that I or Norbert Preining look into this and come back with a more constructive proposal. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt installtion and Debian
Norbert Preining [EMAIL PROTECTED] wrote:
* TEXFONTMAPS is also wrong: it makes pdftex (and dvipdfmx as well,
I guess) find the mapfiles for dvips before their own mapfiles
(those are shipped with ConTeXt).
I have:
TEXFONTMAPS.dvipdfm = .;$TEXMF/fonts/map/{dvipdfm,dvips,}//
TEXFONTMAPS.dvipdfmx = .;$TEXMF/fonts/map/{dvipdfm,dvips,}//
TEXFONTMAPS.pdftex = .;$TEXMF/fonts/map/{pdftex,dvips,}//
TEXFONTMAPS.pdfetex = .;$TEXMF/fonts/map/{pdftex,dvips,}//
TEXFONTMAPS.xetex= .;$TEXMF/fonts/map/{xetex,pdftex,dvips,}//
TEXFONTMAPS.dvips= .;$TEXMF/fonts/map/{dvips,pdftex,}//
TEXFONTMAPS =.;$TEXMF/fonts/map/{$progname,pdftex,dvips,}//;\
$TEXMF/{$progname,pdftex,dvips}/{config,}//
this works fine (but it is perhaps a bit too verbose).
Debian currently has:
TEXFONTMAPS = .;$TEXMF/{fonts/,}map//;$TEXMF/dvips//
What about this? I am not completely convinced about it since with
updmap we generate input file for all the different programs.
The second part, $TEXMF/dvips//, is a Debian-specific
backwards-compatibility hack to allow fonts to be found that install
their map files according to the old (teTeX 2.0) TDS. We should drop it
as soon as etch is out, and we should probably have done that even
earlier. The first I don't quite understand, we actually have:
% TEXFONTMAPS = .;$TEXMF/{fonts/map,}/{$progname,pdftex,dvips,}//
TEXFONTMAPS = .;$TEXMF/{fonts/,}map//;$TEXMF/dvips//
This looks like we dropped the program-specific paths (and with that
their order), and like it wouldn't have been necessary to add a hack
(but I know that at the time of the teTex-3.0-beta-release when I
introduced it it *was* necessary).
Regards, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Hans Hagen [EMAIL PROTECTED] wrote: [ horror story snipped ] anyhow, by now, no alias file should be present in any tex root any more; it was a bad idea anyway I always thought that the purpose of the aliases file was that a non-existent (no, nay, never, nowhere ever) filename was aliased to an existent one, like in the documentation part: % documentation TETEXDOC.pdf teTeX.pdf etex-man.pdf etex.pdf pdftex-a.pdf pdftex.pdf testeuro.dvi eurosym.dvi If the rest of the aliases covers files that might exist as real files on some systems - I agree, what a bad idea. pool files normally are in web2c paths; future versions of pdftex and mpost have the pool file embedded so this problem will (hopefully) disappear Ah, I didn't know that. pdftex 1.40 doesn't have this already, has it? hm, interesting; lean and mean texmf.cnf files can speed up things a lot when playing with luatex (where i intend to replace kpse completely with a lua based variant) it is possible to have format specific file databases; this runs much faster; this whole ls-r stuff is pretty outdated Oh, yes, it is. Current kpse also has the side effect that on most systems, users are able to fill up the /var/ partition by generating pixel fonts... Karl (or was it Olaf?) once said there are plans for a complete replacement of libkpathsea, named kpse - would that be obsolete with luatex? Could there be a C wrapper about lua's kpse? sure, but (i'm not sure if this is still true) running tex live alongside a tetex was always kind of problematic due to path settings and this autoparent mess then deriving locations of texmf.cnf from it This is probably still a problem in standard-setup systems. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
[NTG-context] ConTeXt on Debian: The wiki entry
Hi everybody, this mail has a double purpose. At the end, there's a call for testers of a new (planned) Debian ConTeXt package that would be updated more frequently than now (at least in unstable and testing), where ConTeXt is tied to teTeX's or TeXlive's release cycles. But first, I'd like to talk about http://wiki.contextgarden.net/Debian_installation Are some of the people around who wrote this? I found some information in it misleading and in part just wrong (this has already been pointed out two weaks ago by plink), and have started to edit the page to change the parts that give us, the Debian TeX maintaines, most headache. But in the lower part, Steps to finish a first context upgrade, I felt lost. If these steps are really needed, then there's something seriously wrong in Debian's (and probably upstream's) packaging of ConTeXt. Therefore I didn't just change the text to reflect how I think it should work. Instead, we should try to figure out together whether it in fact does not work as it should, and then fix the Debian packages (hopefully still possible for etch). So the specific question I have are: - Is it intended that context formats end up in $TEXMF/web2c/pdfetex/? If yes, why is that so? If not, we should rather find out why it happens and fix it. - Why does it make a difference if the formats are created by fmtutil instead of texexec (Except for the output directory)? Should the upstream packaging be changed so that fmtutil is never used, but texexec, or should fmtutil be fixed to produce the same as texexec? Finally, here comes Norbert Preining's Call for Testers: Dear all! We = Debian TeX maintainers searching for users of the Debian Operating Systems which are also using ConTeXt. Currently Debian etch (testing) and sid (unstable) contains packages for TeX live 2005. But this contains a bit old ConTeXt version, so users are asking us to update ConTeXt. We have prepared a updated ConTeXt package for Debian, based on the latest released version (2006.08.08), and would ask you to help use testing, as we are not experienced in ConTeXt type settings. I checked some simple documents from the ConTeXt Garden, and they worked, but more detailed testing would be nice. If you have interest, please contact us at [EMAIL PROTECTED] or, if you have a bit experience, you can straight away add deb http://www.tug.org/texlive/Debian/ context/ to your /etc/apt/sources.list file and install context. After this, please tell us our experiences/failures/suggestions. Thanks a lot and all the best Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Taco Hoekwater [EMAIL PROTECTED] wrote: Hi Frank, Frank Küster wrote: Are some of the people around who wrote this? I found some information I do not use Debian and did not write that page, but I can answer your questions partially, at least. Thank you - yes, this helps. - Is it intended that context formats end up in $TEXMF/web2c/pdfetex/? If yes, why is that so? If not, we should rather find out why it happens and fix it. Yes, it is. ConTeXt does not support only pdfetex, but all major engines, like XeTeX and Aleph. I have formats in: $TEXMF/web2c/aleph/ $TEXMF/web2c/luatex/ $TEXMF/web2c/pdfetex/ $TEXMF/web2c/xetex/ Ah, okay, that's clear. Has this already been this way one year ago when texlive2005 was released? Do you know whether the TeXlive developers are aware of that? - Why does it make a difference if the formats are created by fmtutil instead of texexec (Except for the output directory)? Should the upstream packaging be changed so that fmtutil is never used, but texexec, or should fmtutil be fixed to produce the same as texexec? It is almost certainly better to ignore/block fmtutil and use texexec instead. Properly setting up a ConTeXt update is not necesarily limited to format generation only. Hm. What are the other things that need to be done? This is in fact an issue that affects not only Debian, but TeXlive and probably most TeX distributions. They currently assume that after an update of some files and/or executables, it's sufficient to run mktexlsr (possibly more than once), updmap(-sys) and fmtutil(-sys) --all. If this is not sufficient for ConTeXt, there are two possibilities: - fix fmtutil and updmap so that they do the right thing for ConTeXt - or implement a way to automate calling texexec. This would include using some configuration file, since not everybody who has aleph or xetex installed also wants a context format for this engine. To me, as a TeXlive and teTeX guy, it seems preferrable to choose option 1 and fix the existing distribution scripts. However, I don't know yet what else is needed when ConTeXt is updated, therefore I might be wrong, and switching to texexec might actually be better. But then this should be done consistently, and fmtutil should drop context handling completely (or just call texexec). Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Taco Hoekwater [EMAIL PROTECTED] wrote: To me, as a TeXlive and teTeX guy, it seems preferrable to choose option 1 and fix the existing distribution scripts. However, I don't know yet what else is needed when ConTeXt is updated, therefore I might be wrong, and switching to texexec might actually be better. But then this should be done consistently, and fmtutil should drop context handling completely (or just call texexec). I am very much in favor of using texexec for everything related to ConTeXt. Can you point me to the place where it is documented which calls are needed to be called - when ConTeXt is updated - when any of the engines is updated? I don't use ConTeXt myself, and I always have problems finding the relevant places in the documentation, sorry... Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] ConTeXt on Debian: The wiki entry
Hans Hagen [EMAIL PROTECTED] wrote:
Sanjoy Mahajan wrote:
A system-wide installation, if done cleanly, would be much easier
(as plink pointed out). If you (or 'texexec --make' to generate the
formats) ask kpathsea where to put the format files, it'll give you
a directory in TEXMFHOME, so a per user install. But how do you ask
kpathsea the correct question so that it'll tell you where they
should go for a system-wide install?
you can't and i remember asking for such a feature but ... ;
Can you point me to this discussion? I think it doesn't need more as
what fmtutil-sys, updmap-sys and texconfig-sys do before calling
fmtutil, updmap or texconfig, respectively:
v=`kpsewhich -var-value TEXMFSYSVAR`
c=`kpsewhich -var-value TEXMFSYSCONFIG`
TEXMFVAR=$v
TEXMFCONFIG=$c
export TEXMFVAR TEXMFCONFIG
exec updmap ${1+$@}
However, it would be probably more elegant and context-like to not have
texexec and texexec-sys, but rather a commandline switch - in this case
the handling would have to be done in the perl (or ruby?) scripts, which
is somewhat trickier.
the only
way to figure that out is to check all format paths and take the first
one that fits; unfortunalty the tetex paths are rather messy so it's
hard to predict in what permutation of home, usr, share, sys, opt *
local * tex, TeX, teTeX, whatever * texmf, texmflocal, texmf-local,
texmf-teTeX, texmf-dis, texmf.local, texmf-whocares * web2c,
web2c/engine etc etc a format may end up;
I'm not sure what you mean. The default TEXMF path for teTeX (and I
think also for TeXlive) is
TEXMF =
{!!$TEXMFCONFIG,!!$TEXMFVAR,$TEXMFHOME,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TEXMFMAIN,!!$TEXMFLOCAL,!!$TEXMFDIST}
where the first three are per-user, the others are system trees. An
explanation about installing does not need to know whether, for example,
TEXMFLOCAL is called texmf.local or texmf-local or
/usr/local/share/texmf. The only problem might be that some users
change the order or the trees, but that's not a big problem if we
suggest to use the default path.
this is further complicated
by the fact that kpse has to do some guessing about where it's
configuration files are (web2c, etc, home, nowhere),
This is only a problem if people have more than one texmf.cnf - is this
actually the case? I don't think I ever heard of that.
what trees make
sense, etc etc; and, yes, some of the paths are hard coded in the
binaries, so relocating is tricky ... isn't it magic that tex still
runs -)
AFAIK only the search path for texmf.cnf is hard-coded, and that can't
be avoided. On the other hand, no one ever approached me and requested
a relocation: What would you want, and in which cases?
TIA, Frank
--
Dr. Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX/TeXLive)
___
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
Re: [NTG-context] [tex-live] man page for mptopdf
Hans Hagen [EMAIL PROTECTED] wrote: i happily leave that to users; technically it should be possible to process a manual source (to say mptopdf) so that it produces a man page but not all manuals have the same structure (which means that i'd have to write additional styles); maybe pdftotext somemanual.pdf somemanual.man is enough. As said, i happily leave creating man pages to users so I cc to the context list. Debian people have written manpages for many ConTeXt executables. I even think we have one for each of them now. Here's the one for mptopdf. Regards, Frank mptopdf.1.gz Description: manpage -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX) ___ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
