Re: crypto policy redux
On Fri, 28 Mar 1997, Klee Dienes wrote:
[snip]
> How should I handle the generation of free packages from
> cryptographically restricted sources? As I see it, there are two
> options:
>
> A: Upload the Kerberos source to non-US only, and upload the
> non-crypto packages to the main distribution without source.
> (After all, the source really is freely available, just not
> from the same FTP site).
>
> B: Duplicate the Kerberos source into two source packages, one of
> which builds all the packages, both crypto and non-crypto,
> and the other of which has all cryptographic code removed.
> Upload the former to the main distribution and the latter to the
> non-US site.
Do you create packages with different binary package names? Then I'd vote
for splitting up the upstream source into two different source packages
that create the specific binary packages.
If this should be too much work then I'd prefer having only _one_ source
package located at our non-us site which produces both binary packages.
You should create a "dummy source package" for the main site or place a
your-package-name.README in the source tree to tell the user where to get
the sources.
Thanks,
Chris
-- Christian Schwarz
schwarz@monet.m.isar.de, schwarz@schwarz-online.com,
Debian is looking schwarz@debian.org, schwarz@mathematik.tu-muenchen.de
for a logo! Have a
look at our drafts PGP-fp: 8F 61 EB 6D CF 23 CA D7 34 05 14 5C C8 DC 22 BA
at http://fatman.mathematik.tu-muenchen.de/~schwarz/debian-logo/
Reply to: