Re: NEW: books/rfc again
On 2015 Nov 20 (Fri) at 15:48:46 + (+), Mikolaj Kucharski wrote: :Hi, : :I like simple port shared by Peter few weeks ago. Here is :slightly tweaked version with manpage from David Dahlberg. : :I found this port useful. Comments? : :I didn't address issue with changing rfc-index.txt and bcp-index.txt :files. Should they be packaged by hand and hosted in separate tarball :for example? : :-- :best regards :q# I would much prefer to use the ietf-cli port that sthen@ has submitted. -- A classic is something that everybody wants to have read and nobody wants to read. -- Mark Twain, "The Disappearance of Literature"
Re: NEW: books/rfc again
On 2015/11/20 15:48, Mikolaj Kucharski wrote:
> Hi,
>
> I like simple port shared by Peter few weeks ago. Here is
> slightly tweaked version with manpage from David Dahlberg.
>
> I found this port useful. Comments?
>
> I didn't address issue with changing rfc-index.txt and bcp-index.txt
> files. Should they be packaged by hand and hosted in separate tarball
> for example?
>
> --
> best regards
> q#
Some tips on this ...
- Skip the copying, untar them straight to INSTALL_LOC. This is already
going to be pretty bad enough to decompress the files on slow arch,
don't make them copy them from disk to disk as well.
- SUBST_CMD can be used to copy-and-edit ${FILESDIR}/rfc.sh in one
operation (and same for the manpage which has a hardcoded /usr/local).
- The index problem does need to be handled.
- To avoid huge file downloads when doing pkg_add updates I'd be tempted
to split it up a bit with a 'meta' port (empty, just with RUN_DEPENDS)
to add them.
... though I'm not too sure it's worth the space on the mirrors for
30-odd copies of this (11 arch x snaps + 2 releases) when the files are
rsync'able anyway.
ietf-cli.tgz
Description: application/tar-gz
Re: [NEW] books/rfc
> On 30 Oct 2015, at 16:49, Joerg Jung wrote: > > >> On 30 Oct 2015, at 12:34, Peter Hessler wrote: >> >> I've wanted a local cache of the RFCs for a long time, so I quickly >> wrote up a simple port to keep them local, and a trivial pager helper >> script. >> >> use: $ rfc 2549 >> >> OK? > > Forgot the attachment? Sorry, I see you sent already. Next time I first scroll down, read all mails and then reply. > Have you seen this? http://www.unix-ag.uni-kl.de/~auerswal/rfc-reader/ > >> = >> The RFC series contains technical and organizational documents about the >> Internet, including the specifications and policy documents produced by >> four streams: the Internet Engineering Task Force (IETF), the Internet >> Research Task Force (IRTF), the Internet Architecture Board (IAB), and >> Independent Submissions. >> = >> >> >> -- >> 186,282 miles per second: >> >> It isn't just a good idea, it's the law!
Re: [NEW] books/rfc
> On 30 Oct 2015, at 12:34, Peter Hessler wrote: > > I've wanted a local cache of the RFCs for a long time, so I quickly > wrote up a simple port to keep them local, and a trivial pager helper > script. > > use: $ rfc 2549 > > OK? Forgot the attachment? Have you seen this? http://www.unix-ag.uni-kl.de/~auerswal/rfc-reader/ > = > The RFC series contains technical and organizational documents about the > Internet, including the specifications and policy documents produced by > four streams: the Internet Engineering Task Force (IETF), the Internet > Research Task Force (IRTF), the Internet Architecture Board (IAB), and > Independent Submissions. > = > > > -- > 186,282 miles per second: > > It isn't just a good idea, it's the law! >
Re: [NEW] books/rfc
Peter Hessler writes:
> I've wanted a local cache of the RFCs for a long time, so I quickly
> wrote up a simple port to keep them local, and a trivial pager helper
> script.
I like this idea.
PKGNAME defaults to ${DISTNAME}, so you can remove that line.
Might as well use https consistently for HOMEPAGE/MASTER_SITES/MASTER_SITES0.
The commented MASTER_SITES line should be removed (or the ftp server
should be listed after the https server in MASTER_SITES, but I don't see
much point in that since they're the same source).
rfc-index.txt and bcp-index.txt seem like unstable files that will
become unfetchable (change hashes) often. They already list RFCs that
won't exist in the package. Not sure it makes sense to keep these around.
The mirror has RFCs1001-1500.tar.gz and RFCs7001-7500.tar.gz, but these
aren't included in the port.
You can use sed -i instead of perl -i -pe.
When I try installing:
/usr/ports/pobj/rfc-0.0.7000/bin/install -c -m 644
/usr/ports/pobj/rfc-0.0.7000/rfc*.txt
/usr/ports/pobj/rfc-0.0.7000/fake-amd64/usr/local/share/doc/rfc/
/bin/sh: /usr/ports/pobj/rfc-0.0.7000/bin/install: Argument list too long
Quick hack to fix it: replace
${INSTALL_DATA} ${WRKDIST}/rfc*.txt ${INSTALL_LOC}/
with
.for i in 1 2 3 4 5 6 7 8 9
${INSTALL_DATA} ${WRKDIST}/rfc$i*.txt ${INSTALL_LOC}/
.endfor
--
Anthony J. Bentley
Re: [NEW] books/rfc
Am Freitag, den 30.10.2015, 12:35 +0100 schrieb Peter Hessler: > I've wanted a local cache of the RFCs for a long time, so I quickly > wrote up a simple port to keep them local, and a trivial pager helper > script. There seems to be a RFCs1001-1500.tar.gz missing. Also missing is RFCs7001-7500.tar.gz, or is this set not completed yet? Small final remark: If GNU can add 20 pages of licence around a one- liner script, we might at least add a few lines of mandoc(7). Here you are. .Dd $Mdocdate: October 30 2015 $ .Dt RFC 1 .Os .Sh NAME .Nm rfc .Nd shows text from local collection of RFCs .Sh SYNOPSIS .Nm .Ar number .Sh DESCRIPTION .Nm will show the RFC referenced by .Ar number in a .Ev PAGER . .Sh ENVIRONMENT .Bl -tag -width Ds .It Ev PAGER The .Ev PAGER to be used. Default: less. .El .Sh FILES .Bl -tag -width Ds .It Pa /usr/local/share/doc/rfc/rfc-index.txt Index of locally available RFCs. .El .Sh EXIT STATUS .Ex -std .Sh EXAMPLES $ rfc 2549 .Sh SEE ALSO .Xr less 1 .Sh HISTORY The .Nm command was first released on 30 Oct 2015. .Sh AUTHORS .An Peter Hessler Aq Mt phess...@openbsd.org
