Re: the rfc package control file
On Thursday, May 15, 2003, at 05:43 AM, Martin Quinson wrote:
Source: rfc
Section: non-free/doc
Priority: optional
Maintainer: Martin Quinson <Martin.Quinson@tuxfamily.org>
Build-Depends-Indep: debhelper (>> 3.0.0)
Standards-Version: 3.5.2
Package: rfc-tools
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901),
doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901),
doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901),
doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901),
doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901),
doc-rfc-std-proposed (<< 20020901)
Description: Searching tools for RFCs
The Requests for Comments (RFCs) form a series of notes, started in
1969,
about the Internet (originally the ARPANET). The notes discuss many
aspects
I suggest "originally called ARPANET"
of computer communication, focusing on networking protocols,
procedures,
programs, and concepts but also including meeting notes, opinion, and
sometimes humor. See RFC2026 (in package rfc-bcp) for more
information.
.
This package contains some searching tools about the RFCs.
Some tools for searching RFCs?
Package: rfc-unclassified
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901),
doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901),
doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901),
doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901),
doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901),
doc-rfc-std-proposed (<< 20020901)
Description: RFCs which don't fit in other packages
[...]
.
This package contains various RFCs whose status is 'unknown'.
Suggestion: ... whose status is not known.
Possibly include an explanation about why the status can be unknown.
Package: rfc-standard
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901),
doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901),
doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901),
doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901),
doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901),
doc-rfc-std-proposed (<< 20020901)
Description: Standard RFCs
[...]
.
This package contains the 'standards' RFCs. This is the third and last
maturity level for standard tracks. Please note that FYI and BCP
standards
are in their own package. From RFC2026:
This package contains the internet standard RFCs. These are the most
mature RFCs and describe some of the most fundamental parts of the
Internet. This is the final stage on the Standards Track. From RFC 2026:
.
[...]
.
Please note that FYI and BCP RFCs are each in a separate package.
Package: rfc-standard-old
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901),
doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901),
doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901),
doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901),
doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901),
doc-rfc-std-proposed (<< 20020901)
Description: Obsoleted standards
RFC stands for Request For Comment. Those documents are meant to
become
Internet Standards after a maturiting process described in RFC2026
(which
can be found in package rfc-bcp).
Why did the boilerplate suddenly change here?
Package: rfc-fyi
Architecture: all
Conflicts: doc-rfc (<< 20020901), doc-rfc-0001-0999 (<< 20020901),
doc-rfc-1000-1999 (<< 20020901), doc-rfc-2000-2999 (<< 20020901),
doc-rfc-3000-3999 (<< 20020901), doc-rfc-experimental (<< 20020901),
doc-rfc-fyi-bcp (<< 20020901), doc-rfc-misc (<< 20020901),
doc-rfc-old-std (<< 20020901), doc-rfc-std (<< 20020901),
doc-rfc-std-proposed (<< 20020901)
Description: For Your Information RFCs
This package contains the FYI serie of RFCs (For Your Information).
s/serie/series
Reply to: