how to check siunitx package installed or not

Mike Marchywka marchywka at
Fri May 8 12:43:47 CEST 2020

The screen shots don't mean anything to me but on a quick google search
this does come up with expl3 which I recall was another problem that 
I think went away on upgrading. There are a few reports of siunitx incompatibilities,

I guess the versions are one problem and maybe it can't find the right one,

this mentions l3,

and you can check ctan for any other comments on issues.;%20charset=ISO-8859-1&header=1

but not sure if these are relevant to you or my old problem.

note new address
 Mike Marchywka 306 Charles Cox Drive Canton, GA 30115
 2295 Collinworth  Drive Marietta GA 30062.  formerly 487 Salem Woods Drive Marietta GA 30067 404-788-1216 (C)<- leave message 989-348-4796 (P)<- emergency

From: texhax < at> on behalf of political science <tapas.abhitech at>
Sent: Friday, May 8, 2020 6:10 AM
Cc: texhax at
Subject: Re: how to check siunitx package installed or not

I dont have any miktex paackage manager, I checked
this answer
Here are three screenshots of my system



you can see.

On Fri, 8 May 2020 at 15:28, Mike Marchywka <marchywka at<mailto:marchywka at>> wrote:
I just made a bunch of scripts to modify the kpse variables so when I start a latex
project it takes the system values and adds stuff to the front as well as back...
In theory anyway the system values can change and this is a transparent prepend.
or append.
The syntax IIRC was a bit different for normal paths ( something about descending into
subdirs ) but logic similar.
From: texhax < at< at>> on behalf of Peter Flynn <peter at<mailto:peter at>>
Sent: Friday, May 8, 2020 5:52 AM
To: texhax at<mailto:texhax at>
Subject: Re: how to check siunitx package installed or not

On 08/05/2020 10:30, Mike Marchywka wrote:
> I expected some issues with this and created a bunch of places to
> prepend search paths for locations to dump candidate packages that
> may fix problems with current ones lol.  Quickly grepping my
> directories and scripts though I'm not sure if everything did finally
> work without a lot of kluges..

This is why I recommend using the standard personal TeX directory idea:
it saves having to edit paths that will get overwritten by a version update.


More information about the texhax mailing list.