Re: postinstall: fontconfig abnormal exit

[ASSI <Stromeko@nexgo.de>]

Ken Brown via Cygwin writes:
> There's no dependency relation between libxml2 and
> libfontconfig-common, so #4 wouldn't fix the problem.

You'd have to introduce a provides you could depend on, yes.

> And some of the other suggestions would require work on setup.exe that
> someone would have to do.  The current problem is simple to fix and
> shouldn't have to wait for that.

Sure, I was just pointing out that these things have a spectrum of both
inherent and solution complexity.  Activating an additional postinstall
stratum is in fact just adding one character to one constant string in
postinstall.cc, but how to actually use it would be a more involved
discussion.

> I like your idea of using perpetual postinstall scripts.  I think the
> way to do it is probably to make fontconfig_dtd.sh perpetual with
> prefix "zp_".

Yes, that seems like a better solution.  I see a lot of the texlive
stuff already works this way and it appears to have no problems.  While
you're at it, please make it a dash script unless you really need
bashisms.

> That way if libfontconfig-common is installed without
> libxml2 but then libxml2 is installed later, the xmlcatalog command
> gets run.  We would have to check that no harm is done if that
> xmlcatalog command gets run more than once.

From memory, I think as long as you only "--add/--del" then that should
work, but "--create" would clobber any existing content.  So libxml2
postinstall should install the default/empty catalog file and then any
other package should just add/delete the entries that are under control
of that package.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada