On 18 Apr 1998, James Troup wrote:
> Hi,
>
> Santiago approached us (pgp-update) about splitting the debian-keyring
> from doc-debian because a) the keyring tar ball is currently 256Kb
> (36% of doc-debian's installed size) and growing (it may eventually
> double in size when I get round to adding a debian-keyring.gpg) and b)
> the keyring is updated much more frequently than doc-debian needs to
> be (doc-debian wasn't updated for 7 months at one point).
>
> So we intend to create a debian-keyring package which will be uploaded
> weekly (if there are no changes, there'll be no upload, but given the
> last couple of months I don't anticipate that RSN). It'll be
> maintained by "Igor Grobman and James Troup <[EMAIL PROTECTED]>".
> I know this is controversial, but quite frankly, I don't care. The
> current ``policy'' was invented by Christian with zero consultation
> (he ``thought it was already policy''[1]) and until it's ratified by
> the developers I will ignore it as much as I ignored the bogus
> no-ldconfig FUD in the packaging manual prior to 2.4.0.1.
>
> Personally I think this package could go into hamm since it is a) not
> really new but is a derivative of a package already in hamm, b) Arch:
> all, c) very simple, it's hard to imagine release-critical errors one
> could make in packaging it. But if Brian disagrees I won't argue the
> point and it'll go to slink.
>
> Any objections? (To the package itself, only please; take any
> comments about the multiple-maintainership to debian-policy)
>
As to the package: Go for it!
As for the Policy violation: Go for it!
I've said this before, and I know that some disagree, policy is a set of
guidelines, not a straight jacket.
Luck,
Dwarf
--
_-_-_-_-_- Author of "The Debian Linux User's Guide" _-_-_-_-_-_-
aka Dale Scheetz Phone: 1 (850) 656-9769
Flexible Software 11000 McCrackin Road
e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308
_-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
