Re: kernel-patch-int, non-us and non-free.

[Robert van der Meulen <rvdm@cistron.nl>]

Quoting Marcin Owsiany (porridge@pandora.info.bielsko.pl):
> We should remember, that the problem is not only US export restrictions.
> For examples some countries do not allow crypto at all, so the name
> "non-us" also warns other people (though the name is not best - maybe we
> should rename it to 'crypto'?).
Good point.
I must admit i didn't think of 'other countries' ;)
A 'crypto' section sounds nice, but the problem is that that might be a bit
too specific, while i think 'non-us' is too general (and too specific too,
as it limits things to a single country).
Maybe something like 'restricted', or something.
It's a pity we can't have a system to allow single packages to be
mirrored, or have a system to accept/reject mirroring for specific countries
on a per-package basis.
If i throw everything in non-us, it means that i restrict the US on some
stuff that they _can_ have (as far as i know).
If some countries do not allow crypto at all - how do we do it with the
password files, gpg keys, package signing,<insert other (almost) mandatory
crypto here> ?

Greets,
	Robert

-- 
|      rvdm@cistron.nl - Cistron Internet Services - www.cistron.nl        |  
|          php3/c/perl/html/c++/sed/awk/linux/sql/cgi/security             |
|         My statements are mine, and not necessarily cistron's.           |
              "Cleveland? Yes, I spent a week there one day."