This is the mail archive of the
mailing list for the Cygwin project.
Re: unofficial packages
----- Original Message -----
From: "Charles Wilson" <firstname.lastname@example.org>
To: "Robert Collins" <email@example.com>
Sent: Thursday, July 11, 2002 10:17 AM
Subject: Re: unofficial packages
> Robert Collins wrote:
> > Yes, this requires documenting who maintains packges, but it doesn't
> > be easily available to end users (i.e. the user interface doesn't have
> > expose it).
> Hmmm...so *setup* would have to know who maintains what, as far as
> official packages go. Now, this can't be compiled-into the executable;
> it has to be distributed from the mirrors. Are you thinking encryption?
> 'cause that's pointless -- the decryption key has to be bound into
> setup.exe; thus, available from setup's sources.
No, I'm think it's part of the setup.bz2 file. It's not like folk need to
read that themselves, and as you say, cygwin-announce already documents
every maintainer. And we could do something like:
Give every official maintainer an @cygwin.com address, and those addresses
point straight into firstname.lastname@example.org for maintainers that object to private
This means that:
gpg can validate email@example.com on the key chain.
No one knows your personal email.