public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Thomas Wolff <towo@towo.net>
Cc: cygwin-apps@cygwin.com
Subject: Re: [ITP] man-italic
Date: Sat, 29 Apr 2017 12:36:00 -0000	[thread overview]
Message-ID: <3ddde0b4-f603-0dec-17c4-5aa1ed7a8e7e@dronecode.org.uk> (raw)
In-Reply-To: <31684ee3-b4b7-abea-4e82-8f63e4cd106a@towo.net>

On 21/04/2017 08:59, Thomas Wolff wrote:
> Am 19.04.2017 um 20:38 schrieb Jon Turney:
>> On 28/09/2016 20:46, Thomas Wolff wrote:
>>> The man-italic wrapper scripts enable italic display in manual pages
>>> (where italic is specified in the page) in terminals supporting
>>> italic mode.
>>>
>>> wget http://towo.net/cygwin/man-italic/man-italic-0.9-0.tar.bz2
>>> wget http://towo.net/cygwin/man-italic/man-italic-0.9-src.tar.bz2
>>> wget http://towo.net/cygwin/man-italic/setup.hint
>>
>> This seems to have fallen through the cracks and been completely
>> forgotten.  Sorry about that.
> Fine you noticed anyway:)
>
>> Looking at this, I see that this is not a cygport package.  While this
>> is something which has been done historically, and I know it may seen
>> overkill for something this small, it's something I'm very reluctant
>> to see in new packages.
> As you say, overkill; I've fiddled around with cygport a few times
> already and I can't say I'm happy with it. While it seems to be
> powerful, especially basic use isn't documented in a basic way... Would
> you have a pattern for a script-only package for me, or even ready-to-use?

We could certainly do with some commented examples of cygport files in 
the packaging guide, but SHTDI...

Here's an attempt at a man-italic.cygport:

NAME=man-italic
VERSION=0.9
RELEASE=0
ARCH=noarch

LICENSE="Public Domain"
CATEGORY="Utils Doc"
SUMMARY="Enabling italic display in manual pages"
DESCRIPTION="man-italic installs two scripts and hooks them into the 
workflow of the 'man' command so that the italic attribute of manual 
pages is actually displayed in italics in terminals that support it."

SRC_URI="https://github.com/mintty/man-italic/releases/download/${VERSION}/man-italic-${VERSION}.tar.bz2"
SRC_DIR="man-italic"

src_compile() {
     :
}

src_install() {
     cd ${S}
     doman man-italic.7
     insinto /usr/share/${NAME}
     doins grotty iroff
     insinto /etc/postinstall
     newins postinstall ${NAME}.sh
     insinto /etc/preremove
     newins preremove ${NAME}.sh
}

>> The license which applies to the original work here needs to be stated.
> Checking the package contributor's guide, a license does not seem to be
> strictly necessary, so I thought for a simple thing it could go as
> public domain implicitly. But if you prefer, I'll attach a gnu to it.

Public domain is fine.  But we need a statement inside the source 
package what license applies.

I hope you can see that this is a simple consequence of the need to know 
that we can distribute the package.

>> It would be helpful if the description clarified that what this does
>> is "show italic text in man pages properly as italic, rather than as
>> underlined"
> You mean the sdesc one-liner, not ldesc? I'd like to include the
> "enabling" aspect because the package does not do the actual display
> itself and does not need to be invoked as a tool, like:
> sdesc: "Enabling proper italic display of italic text in man pages,
> rather than underlined"

It's more that I was so used seeing underlined text in my manpages I 
didn't realize that it was supposed to be italic :-)

>> That said, this works and is pretty cool. Nice!
> Thanks. Would that be a "GTG" after sorting out the issues, or are still
> 3 supporters needed as there used to be?

Thinking about this a bit more, I have concerns about the 
preremove/postinstall scripts.

These certainly won't correctly handle the groff package being upgraded.

Is it possible to change groff to use alternatives so this package can 
take over grotty?  Or patch this into groff and have this package just 
install an indicator file which turn on that behaviour?

  reply	other threads:[~2017-04-29 12:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 19:46 Thomas Wolff
2017-04-19 18:38 ` Jon Turney
2017-04-21  7:59   ` Thomas Wolff
2017-04-29 12:36     ` Jon Turney [this message]
2017-04-29 15:51     ` 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=3ddde0b4-f603-0dec-17c4-5aa1ed7a8e7e@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin-apps@cygwin.com \
    --cc=towo@towo.net \
    /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).