From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Providing/Packaging a Postinstalled SUSV4 Doc only Package a la Debian
Date: Mon, 06 Mar 2017 20:42:00 -0000 [thread overview]
Message-ID: <ab6f438b-b052-bf7f-5a8f-38f8e41b4cc9@SystematicSw.ab.ca> (raw)
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
Debian provides a SUSV4 package which downloads the tar.bz2 and installs
the HTML tree from:
http://pubs.opengroup.org/onlinepubs/9699919799/download/
in the postinstall script, as they believe that complies with the terms
permitting individual download stated and linked at:
http://pubs.opengroup.org/onlinepubs/terms.htm
http://www.opengroup.org/legal
Is there any interest in such a package in Cygwin, and is this approach
acceptable?
I have found it useful as it gives me local access to the latest POSIX
specs without needing to find the URL and go on the network.
If there is interest and the approach is acceptable, can cygport
produce a package consisting of only a doc directory and a
postinstall script?
I use cygport to download and build net packages of interest to me,
and maintain a local repo of them, so the regular packaging process is
familiar, including producing cygport, hint, and setup.ini files.
So if cygport won't work here, I can hand code whatever files are
required to provide a package.
As an example, I have attached the script I used as a text file so it
should appear inline and pass sourceware and any personal or corporate
mail filters, unless they scrub all kinds of attachments.
If this is not acceptable for packaging for any reason, I can put the
script up on github and mention it on the main list.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
[-- Attachment #2: etc-postinstall-susv4-sh.txt --]
[-- Type: text/plain, Size: 499 bytes --]
#!/bin/sh
# /etc/postinstall/susv4.sh - Cygwin SUSV4 download and install
# based on Debian sus/susv4 packages to comply with individual download terms
dl=http://pubs.opengroup.org/onlinepubs/9699919799/download/
doc=/usr/share/doc/susv4
tmp=${TMPDIR:-/tmp}
tbz=$(/usr/bin/wget -q -O- $dl | \
/bin/sed '/\.tar\.bz2/!d;s/^.*href="\([^">]\+\.tar\.bz2\).*$/\1/') && \
/usr/bin/wget -N -nv -P $tmp/ $dl$tbz && \
/bin/mkdir -p $doc/ && \
/bin/tar -xf $tmp/$tbz -C $doc/ && \
/bin/rm -f $tmp/$tbz
next reply other threads:[~2017-03-06 20:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 20:42 Brian Inglis [this message]
2017-03-10 15:43 ` David Stacey
2017-03-10 20:10 ` Corinna Vinschen
2017-03-10 20:24 ` Achim Gratz
2017-03-10 21:00 ` David Stacey
2017-03-17 19:41 ` Brian Inglis
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=ab6f438b-b052-bf7f-5a8f-38f8e41b4cc9@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).