Re: SSL binaries
>>>>> "Luca" == Luca Filipozzi <firstname.lastname@example.org> writes:
Luca> On Fri, Feb 02, 2001 at 11:26:46PM +0100, Stefan Hornburg
>> I'm working on a package where multiple binary packages comes
>> from one source package. One binary is linked against libssl,
>> but otherwise independent from the other stuff (couriertls).
>> How is the situation with non-US ? Should all packages goto
>> non-US (urgh) or is there an alternative solution ?
Luca> If the source package produces non-US binaries, then the
Luca> whole thing must go into non-US.
a) the source code doesn't contain crypto code
b) the source code has been configured to disable linking to crypto code.
Would the package still have to go in non-US?
the compiled package doesn't "depend: non-us-package", but
recommends/suggests it instead (ie. it will run fine even without it
installed), is that still a problem? There is at least one package in
the main archive which does this.
Brian May <email@example.com>