There is a dialog based texconfig tool being devised. But it is not yet usable. I hope it will help in configuring various parts of the system. In the mean time, here are some piece of advice in making fpTeX more usable and easily upgradable.
So, the best place to keep your additional stuff is the local texmf tree, which is <root>/texmf-local by default, and which value you can retrieve by typing in a command prompt:
c:\>kpsewhich --expand-var $TEXMFLOCAL c:/Local/TeXLive/texmf-local |
There are two conditions to fulfill :
If you have a look at the definition of $TEXMF, you will find something more or less like:
TEXMF={$HOMETEXMF,!!$TEXMFVAR,!!$TEXMFLOCAL;!!$TEXMFMAIN} |
This setting means, that Web2C will first look for files in your home texmf tree, then in your variable texmf tree, then in your local texmf tree and then in the main texmf tree. The exclamation marks (!!) indicate that Web2C will use the file database for this texmf tree to find files. For this reason, don’t forget to run mktexlsr to update the file database if you install additional files in your local texmf tree.
The best way is to have a home texmf tree for every user. Create a home texmf tree for the user, e.g. c:\donald\texmf for user Donald. Under Windows NT, it is assumed that c:\donald is user Donald’s home directory. Windows 9x users usually do not have home directories.
Copy the file c:\Local\TeX\texmf\web2c\texmf.cnf into the web2c directory of the local texmf tree for the user, e.g. c:\donald\texmf\web2c.
Change this local copy of the file texmf.cnf to use the local texmf tree as explained in section 6.2. Uncomment the line setting the HOMETEXMF variable and set it to :
HOMETEXMF=c:/donald/texmf |
and modify TEXMF to reference it :
TEXMF={$HOMETEXMF,!!TEXMFLOCAL,!!TEXMFMAIN} |
It is not mandatory to put !! in front of HOMETEXMF, because you are not supposed to store thousands of files there. Would you require that only ls-R database be searched, you will need to build it using either the mktexlsr command or the shortcut in the fpTeX menu.
Set the environment variable TEXMFCNF to the local texmf tree of the user, e.g.:
TEXMFCNF=c:\donald\texmf\web2c |
Let us first discuss where generated pk files are stored. By default, mktexpk stores the font in
c:\Local\TeX\texmf\fonts\pk\mfmode\supplier\typeface\fontname.xxxpk |
where xxx is the resolution of the font and the values for supplier and typeface are taken from the path of the mf file that was used to generate the pk file.
Examples:
C:\TeX\texmf\fonts\source\public\cm\cmr10.mf
Supplier = public; typeface = cm
C:\TeX\texmf\fonts\source\jknappen\ec\ecrm1000.mf
Supplier = jknappen; typeface = ec
You can configure where the mktex programs will place the produced files by setting the MT_FEATURES variable in the file mktex.cnf. The following settings are allowed:
Important note: Be sure to set the VARTEXFONTS variable to a proper setting if you use this feature. For this edit the file texmf.cnf (you can use kpsewhichtexmf.cnf to find out where it is located, normaly in ...\texmf\web2c), find the line where VARTEXFONTS is defined (VARTEXFONTS=...) and set it to the proper directory. One interesting directory to set VARTEXFONTS to is $TEXMFLOCAL/fonts. This way, all users at your site will share generated fonts files.
To change the MT_FEATURES setting proceed as follows.
: ${MT_FEATURES=setting1:setting2:setting3} |
c:\Local\TeX\texmf\web2c> copy con mktexnam.opt ^Z |
Applying the previous hints, you can devise your own network installation quite easily.
All the support files, everything except the files in the bin/win32 are shareable with a teTeX or Unix TeX-Live installation. That means you can use samba either to mount from a Windows NT server to a Unix workstation or the converse. Several strategies are possible:
These schemes should have been handled by the InstallShield installer. But so many problems rose up with this installer that these features have been delayed to the next version of the setup program.