From: Thomas Wolff <towo@towo.net>
To: Jon Turney <jon.turney@dronecode.org.uk>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] italic-man
Date: Sun, 25 Jun 2023 15:59:17 +0200 [thread overview]
Message-ID: <9069527f-5b55-699a-1ca2-1c68f87b75ba@towo.net> (raw)
In-Reply-To: <582b84f6-b7e0-9f2b-4b41-828d500b923c@dronecode.org.uk>
Am 25.06.2023 um 15:36 schrieb Jon Turney:
> On 21/06/2023 22:45, Thomas Wolff via Cygwin-apps wrote:
>>
>> Am 16.02.2023 um 20:17 schrieb Thomas Wolff via Cygwin-apps:
>>>
>>> Am 16.02.2023 um 19:59 schrieb Jon Turney:
>>>> On 21/01/2023 17:04, Thomas Wolff via Cygwin-apps wrote:
>>>>> italic-man installs two scripts and hooks them into the workflow
>>>>> of the 'man' command so that the italic attribute of manual pages
>>>>> is actually displayed as italics in terminals that support it.
>>>>>
>>>>> cygport file attached
>>>>
>>>> Thanks very much for having another go at this.
>>>>
>>>> I'm still not overly keen on postinstall/preremove scripts which
>>>> modify a configuration file belonging to another package, so I
>>>> think I'm going to defer to Achim on approving this.
>>>>
>>>> Taking a step back, may I ask a couple of questions?
>>>>
>>>> - Can this be done as a patch to man-db and/or groff?
>>>>
>>>> (perhaps with a separate man-italic package which just contains a
>>>> marker file which enables the functionality?)
>>>>
>>>> - (If different) how would this be done in an upstreamable way?
>>> Thanks for taking a look.
>>> I understand your hesitation but there are a number of zp_
>>> postinstall scripts around that make updates to mandb, mime db,
>>> desktop, various caches, maybe crontab.
>
> There's a difference between updating a cache or db of files which
> exist on the filesystem after the package update and modifying a file
> which might be overwritten by reinstalling or updating a different
> package.
>
>>> Well, yes, there could be a zp_ script for man that makes this entry
>>> to /etc/man_db.conf itself in the presence of the italic-man
>>> package. If that's desired and someone else updates man, I will
>>> cooperate on this.
>>> I think the installation of italic-man does this in an upstreamable
>>> way except for the postinstall mechanism of course which seems to be
>>> different (if existent at all) everywhere.
>>> Thomas
>> I've added a zp_man-db-italic.dash postinstall script as a proposal
>> for man-db to address your concerns, to be found in the repository
>> github.com/mintty/italic-man. However, I find not documentation about
>> these zp_ things, it seems they are just all called after each setup. So
>
> They are briefly covered in [1]. If that's missing some details,
> please let me know and I'll see what can be done to improve it.
>
> [1] https://cygwin.com/packaging-package-files.html#postinstall
>
>> would it actually make a difference whether the zp_ is a script of
>> italic-man or of man-db? I've also added a cygport file to the
>> repository so you can try the update if you like.
Still interested in your opinion about this question. Also whether it's
OK that package italic-man provided a zp script that modified
/etc/man_db.conf.
>> About your first question
>>> - Can this be done as a patch to man-db and/or groff?
>> Do you mean the whole thing should not be a separate package at all
>> but completely patched into man-db?
>
> Well, yes, that would avoid all the knots caused by post-install
> scripts with uncertain ordering I'm worrying about.
I think I have addressed those uncertainties and the problem with the
man-db patch is that man-db package maintainers would need to take up
the issue...
>
> Can you explain, in general terms, why this isn't a feature of stock
> man-db already?
There is option grotty -i in stock man-db but grotty is a tool deeply
embedded in the man toolchain and there is no user-friendly documented
way to inject this option into the toolchain, other than replacing
grotty with a wrapper script which is effectively all my package does.
>
>> Looking forward to your opinion and that of the man-db package
>> maintainer.
>> And yes, the hook works on Linux too, so it could be provided somehow
>> upstream.
>
> Thanks continuing to grind away at this.
>
next prev parent reply other threads:[~2023-06-25 13:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 17:04 Thomas Wolff
2023-02-16 18:59 ` Jon Turney
2023-02-16 19:17 ` Thomas Wolff
2023-06-21 21:45 ` Thomas Wolff
2023-06-25 13:36 ` Jon Turney
2023-06-25 13:59 ` Thomas Wolff [this message]
2023-06-25 16:02 ` ASSI
-- strict thread matches above, loose matches on Subject: below --
2019-07-28 6:01 Thomas Wolff
2019-08-09 12:59 ` Jon Turney
2019-08-09 15:07 ` Ken Brown
2019-08-09 18:56 ` Achim Gratz
2019-08-09 19:31 ` Thomas Wolff
2019-08-09 20:51 ` Brian Inglis
2019-08-10 9:07 ` Thomas Wolff
2019-08-10 21:39 ` Thomas Wolff
2019-08-10 22:29 ` Brian Inglis
2019-08-11 9:33 ` Thomas Wolff
2019-08-11 16:17 ` Achim Gratz
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=9069527f-5b55-699a-1ca2-1c68f87b75ba@towo.net \
--to=towo@towo.net \
--cc=cygwin-apps@cygwin.com \
--cc=jon.turney@dronecode.org.uk \
/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).