public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: FAO perl-XML-SAX maintainers: request for pre-filling ParserDetails.ini
Date: Mon, 09 Apr 2018 17:53:00 -0000	[thread overview]
Message-ID: <87in90p8qb.fsf@Rainer.invalid> (raw)
In-Reply-To: <20180409133440.GA2806@dinwoodie.org> (Adam Dinwoodie's message	of "Mon, 9 Apr 2018 14:34:40 +0100")

Adam Dinwoodie writes:
> Would it be possible for the perl-XML-SAX package to add a post-install
> step per <http://perl-xml.sourceforge.net/faq/#parserdetails.ini>?

Sure, it is possible.  :-)

> Specifically, the instructions there say:
>
>> If you are packaging `XML::SAX` in an alternative distribution format
>> (such as RPM), your post-install script should check if
>> `ParserDetails.ini` exists and if it doesn't, run this command:
>> 
>>     perl -MXML::SAX -e "XML::SAX->add_parser(q(XML::SAX::PurePerl))->save_parsers()"
>
> This would avoid the (apparently benign but irritating) error message I
> see when attempting to build things like the Git documentation
> complaining that the system "could not find ParserDetails.ini".

Hmm.  I'm not too sure this would work correctly in the face of other
changes in the installation.  But then again it's better than nothing.


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

SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

--
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-04-09 17:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 13:34 Adam Dinwoodie
2018-04-09 17:53 ` Achim Gratz [this message]

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=87in90p8qb.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).