Dear fink developers,
Fink's cryptographic directory "crypto" has been moved to become a subdirectory
of "main", in both the stable and unstable trees.
It is no longer necessary to put something into the crypto directory just
because it depends on something else in the crypto directory. The cr
Am Sonntag, 23.03.03 um 03:20 Uhr schrieb Ben Hines:
On Saturday, March 22, 2003, at 03:40 PM, Carsten Klapp wrote:
To summarize, I believe a separate crypto tree is still useful in
Fink. Even if Apple has purchased a licence or permit to distribute
openssl along with Mac OS X, for example, in
On Saturday, March 22, 2003, at 03:40 PM, Carsten Klapp wrote:
To summarize, I believe a separate crypto tree is still useful in
Fink. Even if Apple has purchased a licence or permit to distribute
openssl along with Mac OS X, for example, in Russia, I'm pretty sure
that permit would not automa
On Saturday, March 22, 2003, at 03:33 pm, Max Horn wrote:
I'd be interested to know: does Apple ship this with all version of
Mac OS X in the whole world (I seriously don' know, this not a flame
bait). Neither you nor me probably know this, since we both are in
countries which are not affected
Changing the subject line as this is now really a different discussion.
Ben suggested that we abolish the crypto/ tree.
Disclaimer: I didn't originally invent the crypto/ tree thingy, it was
there before I even joined Fink. Also note that for me, and also for
Ben Hines, there are no legal issue
I'm not sure why python is now in crypto, but I can explain why maxima is:
there is an explicit clause in the license that forbids exporting to
certain locations. The package doesn't depend on anything else which is
in crypto.
-- Dave
---
T
On Saturday, November 9, 2002, at 02:12 PM, Martin Costabel wrote:
My interest in this question comes from the fact that on this machine
here I don't want to install fink's openssl. And since the latest
change in python22, I cannot do fink update-all any more without
having to install openss
I don't want to reopen a general debate about the necessity of the
crypto tree, but it seems to me that there are a couple of packages in
there that don't need to be.
One case is ircii. I cannot see any reason why this is in crypto. Since
I am maintaining it now, I took the liberty to move the
