From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: curl new version docs advice and opinions requested
Date: Sun, 18 Oct 2020 12:43:42 -0600 [thread overview]
Message-ID: <a1d06fd7-f0b4-012c-ce63-75afcec69726@SystematicSw.ab.ca> (raw)
In-Reply-To: <5efdeaf0-36bf-3fb7-5d43-0eaaf7ee2f04@cornell.edu>
On 2020-10-17 16:48, Ken Brown via Cygwin-apps wrote:
> On 10/17/2020 5:38 PM, Brian Inglis wrote:
>> The latest curl version has converted some more docs to md and dropped some, so
>> I'm reconsidering what is packaged with the utility, what is delegated to the
>> -docs package, and whether that should just be included in the -devel package.
>>
>> The following extract from the cygport shows what was included, what I think I
>> should include as it is generally useful, and everything now in the docs
>> directory, such that everything else appears to be likely to be of interest only
>> to developers or maintainers, all shown with sizes below.
> I often use Fedora as a guide when questions like this come up:
>
> https://src.fedoraproject.org/rpms/curl/blob/master/f/curl.spec
Ken, thanks for that pointer: I'll check there; and in future.
Other distros e.g. Debian, aren't as quick on the updates, so no help there.
Fedora provides even less than previous Cygwin, and less than I want to, so I
will go ahead with my choices of small, general docs in the base package, and
include all docs and example code in the -doc package, this release.
Anyone downstream should feel free to pipe up with comments or suggestions.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2020-10-18 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 21:38 Brian Inglis
2020-10-17 22:48 ` Ken Brown
2020-10-18 18:43 ` Brian Inglis [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=a1d06fd7-f0b4-012c-ce63-75afcec69726@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).