actually this is a further comment on corentin's answer, but it exceeds 600 characters.
Since http://www.tug.org/texlive/devsrc/Master/texmf-dist/tex/latex/ is an Apache directory listing you can try downloading packages with wget. For example if you want to download l3experimental where xcoffins is a subfolder you can invoke wget like
wget --cut-dir=4 -np -R "index.html*" -nH -P ~/texmf -r http://www.tug.org/texlive/devsrc/Master/texmf-dist/tex/latex/l3experimental/
or
wget --cut-dir=6 -np -R "index.html*" -P ~/texmf/tex/latex -r http://www.tug.org/texlive/devsrc/Master/texmf-dist/tex/latex/l3experimental/
this.
-P ~/dir/in/home/directory/ specifies the local directory where wget should put your files.-nH tells wget that you don't want to create directories named after the host i.e. ~/texmf/www.tug.org/*/*/ looks not so nice and latex won't find anything under ~/texmf/www.tug.org. But you can omit -nH and change the local directory to -P ~/textmf/tex/latex. Then you have a seperate directory tree that latex also searches.- whereby
--cut-dir=x means that you don't want to create the first x folders of the uri in your local directory (you want to create ~/texmf/tex/latex/l3experimental/ or ~/texmf/tex/latex/www.tug.org/l3experimental/ instead of ~/textmf/texlive/devsrc/Master/texmf-dist/tex/latex/l3experimental).
-R instructs wget to exclude all files beginning with index.html.-r is for recursive fetch- the argument of
-P is the directory where you want to save all those things
-np excludes all parent directories of l3experimental (of course you can find a more detailed description in the manual pages of wget)
but generally be careful if you download things with wget recursively it could mess up a whole directory tree. I would recommend you to first download the files in a temporary directory (for example with -P ~/texmftemporary) where you can examine the downloaded directory tree.
Since latex also searches recursively for packages in ~/texmf/tex/latex you don't have to bother if xcoffins is a subfolder of any other folder/folders.
Of course you can redefine things further if you write a little bash, perl or whatever script that is based on the above command.
Maybe this helps you!?
In your home directory, look in the (hidden) files .bashrc and .bash_profile for lines that include your texlive 2012 path and remove the path. Then add these lines to your .bashrc:
export PATH=/usr/local/texlive/2013/bin/x86_64-linux:$PATH
export MANPATH=/usr/local/texlive/2013/texmf/doc/man:$MANPATH
export INFOPATH=/usr/local/texlive/2013/texmf/doc/info:$INFOPATH
(If you installed texlive somewhere else, or aren't using x86_64, change the paths to point to the correct install directory)
EDIT: I seem to have misunderstood the original question. The above will make sure you're pointing to the correct version of TeXLive (sounds like you might have some 2012 packages installed via your package manager as well). If you want to use a TL installation from a DVD, but packages from your package manager (I don't recommend it, but that sounds like it's what you want to do), you can try creating a dummy TL package so that your package manager will think TL Is installed from it and the dependency chain can be resolved.
Something like the following (from the Tug package on Debian) should do the trick:
- Install vanilla TeX Live as root, system-wide.
- Ensure that the only Debian TeX Live packages installed are tex-common, texinfo, and perhaps lmodern
- Add TeX Live's bin directory to ENV_PATH in /etc/login.defs. [basically what I said above, except that I assume that you might want a different version of TeXLive for different people, hence the use of bashrc).
Tell APT about your TeX Live installation by building a dummy package using equivs:
- $ aptitude install equivs # as root
- mkdir /tmp/tl-equivs && cd /tmp/tl-equivs
- equivs-control texlive-local
edit texlive-local (see below)
- $ equivs-build texlive-local
- $ sudo dpkg -i texlive-local_2011-1_all.deb
At the step "edit texlive-local", edit the Maintainer field and the list of the packages provided by your local TeX Live installation as appropriate. If you installed scheme-full except collection-texinfo as recommended, the file should look like this example.
For more information, see this question.
Best Answer
Instead of messing with the font installations, you may want to simply use the XeTeX engine, which is available through TexLive and is able to use the TrueType fonts installed on the system. Since I'm a Linux user myself, I'm not too sure whether it is installed by default or not. Once it is installed, you can compile your documents with e.g.
instead of the usual
You may want to configure your editor to use xelatex by default. The font declarations with xelatex are very straightforward. For Example
You will need to know the names of the fonts available on your system. This list of names may help you with that.
Note that TexLive also provides the Times font, which is very similar to Times New Roman, and which you can load simply with
\usepackage{mathptmx}. This works with regular pdflatex, so you don't have to install anything. Further, the Helvetica font is very similar to Arial and is available with thehelvetpackage. The LaTeX Font Catalogue provides a good overview of fonts and font packages, many of which are available with TexLive.