I use some .sty-files that are not part of texlive and want to have them in a subdirectory of the folder with my main.tex. I used the following line to load the package:
\usepackage{sty/prettythesis}
This works, but compiling the main.tex with xelatex and using rubber gives me a warning:
sty/prettythesis.sty: You have requested package `sty/prettythesis',
but the package provides `prettythesis'. (page 1)
Is there a way to prevent this warning or handle this case without having to include "sty\" in all .sty-files' \ProvidesPackage command or set the TEXINPUTS environment variable (which seems not to be possible from the main.tex itself)?
I believe this thread here:
talks about precisely the same thing: so it seems, the only alternatives are either using
TEXINPUTS
environment variable; or using the import package. (note, there is a variant on theimport
package on ...Including tex files pg 3.)A bit more about TEXINPUTS:
Hope this helps;
Cheers!
EDIT: I hoped that one could set the TEXINPUTS path directly in the tex file (by using
\write18
-- and note, some versions of LaTeX use--enable-write18
, mine uses-shell-escape
to enable\write18
; see also this) - but it seems it is not possible:... so, now I just call
pdflatex
in my Linuxbash
like this:and then it will resolve directly
\usepackage{mypackage}
in themyfile.tex
file - even ifmypackage.sty
is in a subdirectory, say./subdir/mypackage.sty
.Simply put line below before the call to pdflatex (or latex) in your makefile or build script:
Then reference your package as:
As you discovered, putting the package in a subdirectory (say,
./sty/prettythesis.sty
with respect to your main.tex
file at./
), and calling the package viawill successfully load the package, but it will produce the warning
If all you want is to get rid of this warning, and you're OK with minor modifications in the
.sty
file, then you can simply change the package name that it reports, by changing the\ProvidesPackage
command toThis can be inconvenient if you're going to be moving it around loads, but the modifications load isn't too bad either.
Even better, if what you have in there is a specific, modified version of a standard TeX package (like, say, this patch of natbib), then the change in the package name clearly indicates what package it's providing, and if you reuse the file then it will (most likely) re-raise a warning to prompt you into making sure that you know what you're doing.