public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: setup-x86_64.exe v2.889 doesn't select additionally downloaded packages when installing from local directory
Date: Fri, 23 Mar 2018 21:10:00 -0000	[thread overview]
Message-ID: <ef0ee6c0-02bd-6ee6-2ae4-3078950f8c4b@cornell.edu> (raw)
In-Reply-To: <87efkawxob.fsf@Rainer.invalid>

On 3/23/2018 12:42 PM, Achim Gratz wrote:
> Ken Brown writes:
>>> I think there's no actual dependency of libfontconfig-common on
>>> xmlcatalog, but we lack a triggering mechanism to say "run this
>>> script when this other package is installed"
>>
>> /etc/postinstall/fontconfig_dtd.sh could check whether
>> /etc/postinstall/libxml2.sh exists.  If so, it could run it and then
>> add '.done' so it isn't run again.
> 
> While this seems to maybe solve this particular problem, I really don't
> think that it is a good idea to have postinstall scripts run other
> postinstall scripts and then deactivate them behind the back of
> setup.exe.  Please let's not go there,

I agree.  That was a bad idea.

> if there is a general need to
> coordinate among postinstall scripts let's try to solve that within
> setup (the stratified postinstall concept does allow for something like
> that, it's just not yet fully specified or implemented).

I don't think a general need has been demonstrated.  This is the first 
case I can recall seeing.

I do think that this case should be fixed, one way or another, in 
/etc/postinstall/fontconfig_dtd.sh.  That script assumes, on the basis 
of [ -x /usr/bin/xmlcatalog ], that the catalog /etc/xml/catalog has 
already been created.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2018-03-23 16:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-03 23:00 Robert Cohen
2018-03-03 23:54 ` Brian Inglis
2018-03-04  1:51   ` Robert Cohen
2018-03-04  2:16 ` Ken Brown
2018-03-04  2:32   ` Brian Inglis
2018-03-04  3:01   ` Robert Cohen
2018-03-04  3:11     ` Ken Brown
2018-03-04  4:01       ` Robert Cohen
2018-03-04  5:02         ` Brian Inglis
2018-03-04  5:26           ` Robert Cohen
2018-03-04 15:22         ` Ken Brown
2018-03-06 23:14 ` Jon Turney
2018-03-07  3:37   ` Robert Cohen
2018-03-07 12:15     ` Jon Turney
2018-03-07 20:09       ` Robert Cohen
     [not found]       ` <b03fcc59d6ed4831b4f7c9a225d14466@merl.com>
2018-03-07 20:18         ` Jon Turney
2018-03-22 21:56           ` Ken Brown
2018-03-23 16:54             ` Achim Gratz
2018-03-23 21:10               ` Ken Brown [this message]
2018-03-24  1:05                 ` Brian Inglis

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=ef0ee6c0-02bd-6ee6-2ae4-3078950f8c4b@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@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).