# Run a library from a folder? [closed]

I'm struggling to get Tikz to run on my University terminal, for some as of yet unknown reason, and I don't have the permissions to install Tikz. I've emailed the 'computer help people' asking them to fix it, but that could take anywhere between a day and a month.

I found this question which has gone someway to answering my question, namely this answer. The answer points here and it looks like I want this sort of syntax:

``````\import{/base/otherfolder/million_other_folders}{oneOfTheFiles}
``````

But it seems like this is going to take one line for every file I want, and Tikz is very large.

Am I doing this right? How can I use Tikz without 'installing' it properly?

# Edit the first:

Using `kpsepath tex | sed 's/:/\n/g'` I found that `~/texmf/tex` exists and is accessible to me. Running `tree` on the base `dir` the folders I downloaded look like so, how much of this needs to go into `~/texmf/tex` ?

``````base
|-- doc
|   `-- generic
|-- source
|   `-- latex
`-- tex
|-- context
|-- generic
|-- latex
`-- plain
``````

# Edit the second:

I'm getting conflicting results from `kpsepath tex | sed 's/:/\n/g'|sed '/!!/d'` (I've removed the results appended by `!!` as I think they are folders I don't have permission for.) The issue is I don't think the files it finds don't exist. It may just be my universities set up of this terminal. Here is a screencap:

-

## closed as too localized by Marco Daniel, Joseph Wright♦Apr 15 '12 at 9:13

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center. If this question can be reworded to fit the rules in the help center, please edit the question.

you can type `kpsepath tex | sed 's/:/\n/g` to get an overview of directories that TeX looks in. If an entry ends in `///` it is searched recursively. As @zeroth mentioned `~/texmf` is usually in there, in my case it's actually `~/texmf/tex`. –  Roelof Spijker Feb 9 '12 at 12:53
Well, you can put everything in there, really. TeX searches through it, so you can't really put too much in there (version conflicts aside). It is a good idea to keep it structured though. You can have the same structure under `~texmf` that you now have under `base`. The main thing for compilation will be the `tex` folder though, since that contains the actual packages and code required. The `doc` and `source` folders aren't required, you can have them though if you want to keep the docs and source in your local tree. –  Roelof Spijker Feb 9 '12 at 14:16
Please don't use backticks for blocks of code. Just indent them by 4 spaces so that they get higlighted properly. –  Thorsten Feb 9 '12 at 14:26
The directories you get from `kpsepath` don't necessarilly exist. You can just create them and then put the files in there. –  Roelof Spijker Feb 9 '12 at 14:55
Based on the last comment, this is 'too localised' –  Joseph Wright Apr 15 '12 at 9:13