From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: cygport patches for TeX Live
Date: Thu, 18 Dec 2014 08:22:00 -0000 [thread overview]
Message-ID: <87bnn1z7sn.fsf@Gertrud.fritz.box> (raw)
In-Reply-To: <54920139.1030605@cornell.edu> (Ken Brown's message of "Wed, 17 Dec 2014 17:18:33 -0500")
Ken Brown writes:
> + if [ -d /usr/share/texmf-dist ]
Looks like you'd want
if [ -d ${D}/usr/share/texmf-dist ]
here.
> In postinstall scripts we remove the updmap calls completely and
> instead create a file of commands in /etc/texmf/postinstall, to be run
> by a perpetual postinstall script. In preremove scripts we just group
> the commands into a single call to updmap, since setup.exe doesn't yet
> support perpetual preremove scripts.
I don't really like the idea of using /etc directly for this, what if
every package starts doing that? If /usr/share/<package>/postinstall
doesn't work, we should at least create a subdirectory in /etc for this
purpose.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs
next prev parent reply other threads:[~2014-12-18 8:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 22:49 Ken Brown
2014-12-16 23:08 ` Ken Brown
2014-12-17 22:18 ` Ken Brown
2014-12-18 8:22 ` Achim Gratz [this message]
2014-12-18 9:40 ` Marco Atzeri
2014-12-18 9:41 ` Marco Atzeri
2014-12-18 11:09 ` Achim Gratz
2014-12-18 13:12 ` Ken Brown
2014-12-19 13:19 ` Ken Brown
2015-01-05 7:51 ` Yaakov Selkowitz
2015-01-05 17:04 ` Ken Brown
2015-01-05 17:52 ` Achim Gratz
2015-01-15 21:47 ` Ken Brown
2015-02-12 0:50 ` Yaakov Selkowitz
2015-02-12 4:10 ` Ken Brown
2015-02-12 11:58 ` Ken Brown
2015-02-12 18:40 ` Yaakov Selkowitz
2016-04-15 17:33 Ken Brown
2016-04-17 19:13 ` Yaakov Selkowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bnn1z7sn.fsf@Gertrud.fritz.box \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).