From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: cygport patches for TeX Live
Date: Thu, 12 Feb 2015 11:58:00 -0000 [thread overview]
Message-ID: <54DC9562.8090209@cornell.edu> (raw)
In-Reply-To: <54DC27A3.4060604@cornell.edu>
On 2/11/2015 11:10 PM, Ken Brown wrote:
> On 2/11/2015 7:50 PM, Yaakov Selkowitz wrote:
>> On Thu, 2015-01-15 at 16:46 -0500, Ken Brown wrote:
>>> On 1/5/2015 12:52 PM, Achim Gratz wrote:
>>>> Ken Brown writes:
>>>>> Do you have an opinion about that? I suggested /etc/texmf/postinstall
>>>>> or /var/lib/texmf/postinstall, but Achim had other ideas. The only
>>>>> precedent we have so far is Achim's new _autorebase, which uses
>>>>> /etc/rebase.
>>>>
>>>> Even for this I think /etc is the wrong place and I'd consider
>>>> moving it
>>>> elsewhere. Something in /var on the other hand sounds OK to me.
>>>> LSB/FHS seems to suggest /var/lib for this purpose unless there is yet
>>>> another more specific requirement I didn't find while browsing it.
>>>
>>> In view of https://cygwin.com/ml/cygwin-apps/2015-01/msg00034.html,
>>> I'll use
>>> /var/lib/texmf/postinstall for the postinstall markers. I'm
>>> attaching revised
>>> cygport patches.
>>
>> I applied and pushed patches 1 and 3; given the texlive/fontconfig
>> discussion, does 2 still apply?
>
> Not as it stands. But for users who have chosen to make the TeX Live
> fonts available to fontconfig (by creating a symlink as discussed in the
> other thread), I think I should keep the font caches up to date. I'll
> send a revised patch tomorrow that does this.
On second thought, that patch is OK as is. I'll just change the texlive
perpetual postinstall script so that it only calls fc-cache if the
symlink /etc/fonts/conf.d/09-texlive.conf exists.
Ken
next prev parent reply other threads:[~2015-02-12 11:58 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
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 [this message]
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=54DC9562.8090209@cornell.edu \
--to=kbrown@cornell.edu \
--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).