PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Installieren von Paketen (Kile/SuSE 9.3)



unihiekka
06-10-2005, 20:06
Hallo Leute!

Seit einiger Zeit versuch ich mit LaTeX wissenschaftliche Arbeiten zu schreiben, was an sich gut gelingt, doch nun brauch ich ein Paket von ctan.org, und zwar das Paket feyn (für das Erstellen von Feynman Diagramme). Dazu muss ich es installieren, damit Kile unter Suse 9.3 Pro es erkennt und ich es benutzen kann, aber das habe ich noch nie gemacht und ich weiss nicht, wie sowas geht. Könnte mir jemand da helfen? Was soll ich machen?!

Ich habe folgende Ordner mit texmf:

*) /etc/texmf/ --- Subordner: dvips, pdvips, tex,web2c und xdvi und Datei ls-R
*) /usr/share/texmf/ --- Subordner, u.a.: bibtex, context, doc, dvips, fonts, metafont, tetex, tex, texconfig,scripts,xdvi, ...
*) /var/lib/texmf/ --- Subordner: db, doc, fonts, web2c, xdvi und Datei ls-R

Hier ist meine Datei: /usr/texmf/web2c/texmf.cnf (falls das hilft) - sorry, dass ich auch Teile von Kommentaren dazugemacht habe, aber lieber zu viel als zu wenig :D :

% original texmf.cnf -- runtime path configuration file for kpathsea.
% (If you change or delete `original' on the previous line, the
% distribution won't install its version over yours.)
% Public domain.
%
% Part 1: Search paths and directories.
% The tree containing the runtime files closely related to the specific
% program version used:
TEXMFMAIN = /usr/share/texmf
% The main distribution tree:
TEXMFDIST = /usr/share/texmf/contrib
% A place for local additions to a "standard" texmf tree.
% This tree is not used for local configuration maintained by
% texconfig, it uses TEXMFCONFIG below.
TEXMFLOCAL = /usr/local/share/texmf
% TEXMFSYSVAR, where texconfig-sys stores variable runtime data.
% With teTeX-3.0 or later, this must be set.
% For sharing this tree with $TEXMFMAIN:
% TEXMFSYSVAR = $TEXMFMAIN
% For using a separate tree:
% TEXMFSYSVAR = /usr/share/texmf-var
TEXMFSYSVAR = /var/lib/texmf
% TEXMFSYSCONFIG, where texconfig-sys stores configuration data.
% With teTeX-3.0 or later, this must be set.
% For sharing this tree with $TEXMFMAIN:
% TEXMFSYSCONFIG = $TEXMFMAIN
% For using a separate tree:
% TEXMFSYSCONFIG = /usr/share/texmf-config
TEXMFSYSCONFIG = /etc/texmf
% User texmf trees can be catered for like this...
% This used to be TEXMFHOME.
TEXMFHOME = $HOME/texmf
% TEXMFVAR, where texconfig stores variable runtime data.
% With teTeX-3.0 or later, this must be set.
% For sharing this tree with $TEXMFMAIN:
% TEXMFVAR = $TEXMFMAIN
% For using a separate tree:
% TEXMFVAR = $HOME/.texmf-var
TEXMFVAR = ${TEXMFSYSVAR}
% TEXMFCONFIG, where texconfig stores configuration data.
% With teTeX-3.0 or later, this must be set.
% For sharing this tree with $TEXMFMAIN:
% TEXMFCONFIG = $TEXMFMAIN
% For using a separate tree:
% TEXMFCONFIG = $HOME/.texmf-config
% For using a separate tree:
% TEXMFCONFIG = /usr/share/texmf-config
TEXMFCONFIG = ${TEXMFSYSCONFIG}
% Now, list all the texmf trees. If you have multiple trees you can
% use shell brace notation, like this:
% TEXMF = {$TEXMFHOME,!!$TEXMFLOCAL,!!$TEXMFMAIN}
% The braces are necessary.
%
% For texconfig to work properly, TEXMFCONGIG and TEXMFVAR should be named
% explicitly and before all other trees.
TEXMF = {$TEXMFHOME,!!$TEXMFSYSCONFIG,!!$TEXMFSYSVAR,!!$TE XMFMAIN,!!$TEXMFLOCAL,!!$TEXMFDIST,!!/usr/share/lilypond/2.4.4}
% The system trees. These are the trees that are shared by all the users.
SYSTEXMF = $TEXMFSYSCONFIG;$TEXMFSYSVAR;$TEXMFMAIN;$TEXMFLOCA L;$TEXMFDIST
% Where generated fonts may be written. This tree is used when the sources
% were found in a system tree and either that tree wasn't writable, or the
% varfonts feature was enabled in MT_FEATURES in mktex.cnf.
VARTEXFONTS = /var/cache/fonts
% Where to look for ls-R files. There need not be an ls-R in the
% directories in this path, but if there is one, Kpathsea will use it.
%
% Remove $VARTEXFONTS from TEXMFDBS if the VARTEXFONTS directory is below
% one of the TEXMF directories (avoids overlapping ls-R files).
TEXMFDBS = ${TEXMFHOME};${TEXMFLOCAL};${TEXMFSYSCONFIG};${TEX MFSYSVAR};$TEXMFMAIN;$OLDTEXMF;$VARTEXFONTS;/usr/share/lilypond/2.4.4
% It may be convenient to define TEXMF like this:
% TEXMF = {$TEXMFHOME,!!$TEXMFLOCAL,!!$TEXMFMAIN,$HOME}
% which allows users to set up entire texmf trees, and tells TeX to
% look in places like ~/tex and ~/bibtex. If you do this, define TEXMFDBS
% like this:
% TEXMFDBS = $TEXMFHOME;$TEXMFLOCAL;$TEXMFMAIN;$VARTEXFONTS
% or mktexlsr will generate an ls-R file for $HOME when called, which is
% rarely desirable. If you do this you'll want to define SYSTEXMF like
% this:
% SYSTEXMF = $TEXMFLOCAL;$TEXMFMAIN;$TEXMFDIST
% so that fonts from a user's tree won't escape into the global trees.
%
% On some systems, there will be a system tree which contains all the font
% files that may be created as well as the formats. For example
% TEXMFVAR = /var/lib/texmf
% is used on many Linux systems. In this case, set VARTEXFONTS like this
% VARTEXFONTS = $TEXMFVAR/fonts
% and do not mention it in TEXMFDBS (but _do_ mention TEXMFVAR).

% WEB2C is for Web2C specific files. The current directory may not be
% a good place to look for them.
WEB2C = ${TEXMFHOME}/web2c;${TEXMFSYSCONFIG}/web2c;${TEXMFSYSVAR}/web2c;$TEXMF/web2c

% TEXINPUTS is for TeX input files -- i.e., anything to be found by \input
% or \openin, including .sty, .eps, etc.

% Plain TeX. Have the command tex check all directories as a last
% resort, we may have plain-compatible stuff anywhere.
TEXINPUTS.tex = .;$TEXMF/tex/{plain,generic,}//

% Other plain-based formats.
TEXINPUTS.amstex = .;$TEXMF/tex/{amstex,plain,generic,}//
TEXINPUTS.csplain = .;$TEXMF/tex/{csplain,plain,generic,}//
TEXINPUTS.eplain = .;$TEXMF/tex/{eplain,plain,generic,}//
TEXINPUTS.ftex = .;$TEXMF/tex/{formate,plain,generic,}//
TEXINPUTS.jadetex = .;$TEXMF/tex/{jadetex,plain,generic,}//
TEXINPUTS.mex = .;$TEXMF/tex/{mex,plain,generic,}//
TEXINPUTS.texinfo = .;$TEXMF/tex/{texinfo,plain,generic,}//

% LaTeX 2e specific macros are stored in latex/, macros that can only be
% used with 2.09 in latex209/. In addition, we look in the directory
% latex209, useful for macros that were written for 2.09 and do not
% mention 2e at all, but can be used with 2e.
TEXINPUTS.cslatex = .;$TEXMF/tex/{cslatex,csplain,latex,generic,}//
TEXINPUTS.latex = .;$TEXMF/tex/{latex,generic,}//
TEXINPUTS.olatex = .;$TEXMF/tex/{latex,generic,}//
TEXINPUTS.latex209 = .;$TEXMF/tex/{latex209,generic,latex,}//

% Fontinst needs to read afm files.
TEXINPUTS.fontinst = .;$TEXMF/{tex,fonts/afm}//

% MLTeX.
TEXINPUTS.frlatex = .;$TEXMF/tex/{french,latex,generic,}//
TEXINPUTS.frtex = .;$TEXMF/tex/{french,plain,generic,}//
TEXINPUTS.mllatex = .;$TEXMF/tex/{latex,generic,}//
TEXINPUTS.mltex = .;$TEXMF/tex/{plain,generic,}//

% e-TeX. This form of the input paths is borrowed from teTeX. A certain
% variant of TDS is assumed here, unaffected by the build variables.
TEXINPUTS.elatex = .;$TEXMF/tex/{latex,generic,}//
TEXINPUTS.etex = .;$TEXMF/tex/{plain,generic,}//

% pdfTeX. This form of the input paths is borrowed from teTeX. A certain
% variant of TDS is assumed here, unaffected by the build variables.
TEXINPUTS.pdfcslatex = .;$TEXMF/tex/{cslatex,csplain,latex,generic,}//
TEXINPUTS.pdfcsplain = .;$TEXMF/tex/{csplain,plain,generic,}//
TEXINPUTS.pdfjadetex = .;$TEXMF/tex/{jadetex,plain,generic,}//
TEXINPUTS.pdflatex = .;$TEXMF/tex/{latex,generic,}//
TEXINPUTS.pdfmex = .;$TEXMF/tex/{mex,plain,generic,}//
TEXINPUTS.utf8mex = .;$TEXMF/tex/{mex,plain,generic,}//
TEXINPUTS.pdftex = .;$TEXMF/tex/{plain,generic,}//
TEXINPUTS.pdftexinfo = .;$TEXMF/tex/{texinfo,plain,generic,}//
TEXINPUTS.pdfamstex = .;$TEXMF/tex/{amstex,plain,generic,}//

% pdfeTeX.
TEXINPUTS.pdfelatex = .;$TEXMF/tex/{latex,generic,}//
TEXINPUTS.pdfetex = .;$TEXMF/tex/{plain,generic,}//

% pdfxTeX.
TEXINPUTS.pdfxlatex = .;$TEXMF/tex/{latex,generic,}//
TEXINPUTS.pdfxtex = .;$TEXMF/tex/{plain,generic,}//

% XeTeX
TEXINPUTS.xelatex = .;$TEXMF/tex/{latex,generic,}//
TEXINPUTS.xetex = .;$TEXMF/tex/{plain,generic,}//

% pTeX.
ptex_inputs = .;$TEXMF/{ptex,tex}/{plain,generic,}//
platex_inputs = .;$TEXMF/{ptex,tex}/{platex,latex,generic,}//
TEXINPUTS.platex-sjis = $platex_inputs
TEXINPUTS.platex-euc = $platex_inputs
TEXINPUTS.platex-jis = $platex_inputs
TEXINPUTS.platex = $platex_inputs
TEXINPUTS.ptex-sjis = $ptex_inputs
TEXINPUTS.ptex-euc = $ptex_inputs
TEXINPUTS.ptex-jis = $ptex_inputs
TEXINPUTS.ptex = $ptex_inputs

% Omega / Aleph
TEXINPUTS.lamed = .;$TEXMF/tex/{lamed,lambda,latex,generic,}//
TEXINPUTS.lambda = .;$TEXMF/tex/{lambda,latex,generic,}//
TEXINPUTS.omega = .;$TEXMF/tex/{plain,generic,}//
TEXINPUTS.aleph = .;$TEXMF/tex/{plain,generic,}//

% Context macros by Hans Hagen:
TEXINPUTS.context = .;$TEXMF/tex/{context,plain,generic,}//

% odd formats needing their own paths
TEXINPUTS.lamstex = .;$TEXMF/tex/{lamstex,plain,generic,}//
TEXINPUTS.lollipop = .;$TEXMF/tex/{lollipop,plain,generic,}//
TEXINPUTS.platex-pl = .;$TEXMF/tex/{platex,latex,generic,}//
TEXINPUTS.pdfplatex = .;$TEXMF/tex/{platex,latex,generic,}//

% For xmltex and pdfxmltex
TEXINPUTS.xmltex = .;$TEXMF/tex/{xmltex,latex,generic,}//
TEXINPUTS.pdfxmltex = .;$TEXMF/{pdftex,tex}/{xmltex,latex,generic,}//

% Earlier entries override later ones, so put this last.
TEXINPUTS = .;$TEXMF/tex/{$progname,generic,}//

% Metafont, MetaPost inputs.
MFINPUTS = .;$TEXMF/metafont//;{$TEXMF/fonts,$VARTEXFONTS}/source//
MPINPUTS = .;$TEXMF/metapost//

% Dump files (fmt/base/mem) for vir{tex,mf,mp} to read (see web2c/INSTALL),
% and string pools (.pool) for ini{tex,mf,mp}. It is silly that we have six
% paths and directories here (they all resolve to a single place by default),
% but historically ...
TEXFORMATS = .;$WEB2C
MFBASES = .;$WEB2C
MPMEMS = .;$WEB2C
TEXPOOL = .;$WEB2C
MFPOOL = .;$WEB2C
MPPOOL = .;$WEB2C

% Device-independent font metric files.
VFFONTS = .;$TEXMF/fonts/vf//
TFMFONTS = .;{$TEXMF/fonts,$VARTEXFONTS}/tfm//

% The $MAKETEX_MODE below means the drivers will not use a cx font when
% the mode is ricoh. If no mode is explicitly specified, kpse_prog_init
% sets MAKETEX_MODE to /, so all subdirectories are searched. See the manual.
% The modeless part guarantees that bitmaps for PostScript fonts are found.
PKFONTS = .;{$TEXMF/fonts,$VARTEXFONTS}/pk/{$MAKETEX_MODE,modeless}//

% Similarly for the GF format, which only remains in existence because
% Metafont outputs it (and MF isn't going to change).
GFFONTS = .;$TEXMF/fonts/gf/$MAKETEX_MODE//

% A backup for PKFONTS and GFFONTS. Not used for anything.
GLYPHFONTS = .;$TEXMF/fonts

% A place to puth everything that doesn't fit the other font categories.
MISCFONTS = .;$TEXMF/fonts/misc//;$TEXMF/fonts/hbf//

% font name map files.
TEXFONTMAPS = .;$TEXMF/fonts/map//

% support non"k"-xdvi:
PKFONTS.XDvi = .:$TEXMF/%s:$VARTEXFONTS/pk/{%m,modeless}//
VFFONTS.XDvi = .:$TEXMF/%s
PSHEADERS.XDvi = .:$TEXMF/%q{dvips,fonts/type1}//
TEXPICTS.XDvi = .:$TEXMF/%q{dvips,tex}//

[...]

% Part 2: Non-path options.

[...]

Hoffentlich könnt ihr damit was anfangen...

etilli33
06-10-2005, 20:34
Ich habe mir einfach mal erlaubt, die cnf-Datei nicht zu lesen, weil ich hoffe, sie entspricht dem Standard. ;)
Das Installieren von Paketen mit teTex 2.0 (das ist bei Suse 9.2 dabei) will ich hier kurz erklären, ich schätze, da wird sich bei teTex 3.0 (welches Suse 9.3 liefert) nichts geändert haben:

Prinzipiell werden Pakete in ein Verzeichnis im texmf-Baum abgelegt, da aber deine Einstellungen wohl auch beinhalten, dass dein ~home-Verzeichnis durchsucht wird, lohnt es sich neues Verzeichnis anzulegen, etwa /home/username/texmf, wo dann alle neuen Pakete abgelegt werden. Vorteil: wenn du irgendwann mal updatest oder so, musst du nur noch einen Befehl loslassen und schon hast du alle deine alten Einstellungen wieder da, vorausgesetzt natürlich, du hast die home-Verzeichnisse gerettet.

Also: schaffe z. B. in diesem neuen Verzeichnis Unterverzeichnisse: /tex/latex da werden die meisten Pakete dann in einem eigenen Verzeichnis abgelegt. Du kannst es aber auch anders machen, da ist deiner Phantasie freien Lauf gelassen. Also da hast du jetzt: /home/username/texmf/tex/latex/feyn und darin alle nötigen Dateien. Wenn sie etwa auf dtx oder ins enden, musst du nochmal Latex drüber laufen lassen, um die wirklichen sty-Dateien zu erstellen. Also: du musst am Ende eine sty-Datei finden und evtl. noch andere Dateien, möglicherweise auch eine Dokumentation. Wenn du besonders gerne aufräumst, kannst du die dann auch noch in ein Verzeichnis /texmf/doc/feyn stecken. ;)

Dann gehst du auf eine Kommandozeile und schreibst: texhash Damit werden alle Datenbanken neu aufgebaut, das dauert eine Weile, aber schließlich weiß dann Latex, wo es feyn.sty findet, wenn du es verlangst. So, damit bist du fertig.

Gruß
Till

PS: sprichst du etwa finnisch? Freut mich. :)