public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: ASSI <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] italic-man
Date: Sun, 25 Jun 2023 18:02:51 +0200	[thread overview]
Message-ID: <87bkh3wmvo.fsf@Rainer.invalid> (raw)
In-Reply-To: <9069527f-5b55-699a-1ca2-1c68f87b75ba@towo.net> (Thomas Wolff via Cygwin-apps's message of "Sun, 25 Jun 2023 15:59:17 +0200")


[I've had no time to look at this in detail and that will have to wait a
bit more.]

Thomas Wolff via Cygwin-apps writes:
>>> 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.

In principle I think replacing one tool with another that  has the same
name and slightly different functionality should be done via the
alternatives system, not hand-rolled scripts.  You'd still need
postinstall scripts to set it up correctly.

>>> 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...

I'd prefer that work be one upstream since none of it is specific to
Cygwin, which looks like it would be eminently possible given the nature
of your change.

>> 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.

This is why to me it would make a lot more sense to work with upstream
to come to a solution.  Colin Watson has been pretty receptive in the
past.


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

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

  reply	other threads:[~2023-06-25 16:03 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
2023-06-25 16:02           ` ASSI [this message]
  -- 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=87bkh3wmvo.fsf@Rainer.invalid \
    --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).