Re: crypto patch (OT: ports tree)

2000-11-14 Thread H.C.Hsiang
On Fri, Apr 21, 2000 at 12:29:30PM -0800, Adam Shand wrote: If you're really hard core about security and encryption (and I'm going to be heretical here, but hey, I have to plug my home), try OpenBSD. Since it's main repository is in Canada, US crypto laws don't apply. I played with it

Re: crypto patch (OT: ports tree)

2000-11-14 Thread H.C.Hsiang
On Fri, Apr 21, 2000 at 08:27:52PM -0800, Ethan Benson wrote: and if you want to compile them there's always 'apt-get --compile source packagename'. if you haven't used it before here's how it works :) with the annoying side affect of apt insisting on replacing the locally compiled

Re: crypto patch (OT: ports tree)

2000-04-22 Thread Ethan Benson
On Fri, Apr 21, 2000 at 12:29:30PM -0800, Adam Shand wrote: If you're really hard core about security and encryption (and I'm going to be heretical here, but hey, I have to plug my home), try OpenBSD. Since it's main repository is in Canada, US crypto laws don't apply. I played with it

Apt wishlist WAS: Re: crypto patch (OT: ports tree)

2000-04-22 Thread Marshal Kar-Cheung Wong
Ethan == Ethan Benson [EMAIL PROTECTED] writes: and if you want to compile them there's always 'apt-get --compile source packagename'. if you haven't used it before here's how it works :) with the annoying side affect of apt insisting on replacing the locally compiled

Re: Apt wishlist WAS: Re: crypto patch (OT: ports tree)

2000-04-22 Thread Ethan Benson
On Sat, Apr 22, 2000 at 02:02:35AM -0400, Marshal Kar-Cheung Wong wrote: Ethan == Ethan Benson [EMAIL PROTECTED] writes: and if you want to compile them there's always 'apt-get --compile source packagename'. if you haven't used it before here's how it works :) with

Re: crypto patch (OT: ports tree)

2000-04-22 Thread Brad
On Fri, Apr 21, 2000 at 08:27:52PM -0800, Ethan Benson wrote: and if you want to compile them there's always 'apt-get --compile source packagename'. if you haven't used it before here's how it works :) with the annoying side affect of apt insisting on replacing the locally compiled

Re: crypto patch (OT: ports tree)

2000-04-22 Thread Ethan Benson
On Sat, Apr 22, 2000 at 01:25:15AM -0500, Brad wrote: On Fri, Apr 21, 2000 at 08:27:52PM -0800, Ethan Benson wrote: and if you want to compile them there's always 'apt-get --compile source packagename'. if you haven't used it before here's how it works :) with the annoying side

Re: Apt wishlist WAS: Re: crypto patch (OT: ports tree)

2000-04-22 Thread Jason Gunthorpe
On Fri, 21 Apr 2000, Ethan Benson wrote: I guess ultimately, what would be best, would be to keep track of the sources that you have installed, so that you know when the sources have been updated. Or have apt recompile for you. well i just don't understand why apt thinks it should

Re: Apt wishlist WAS: Re: crypto patch (OT: ports tree)

2000-04-22 Thread Robert D. Hilliard
Ethan Benson [EMAIL PROTECTED] writes: --revision just sets an epoch, which is rather evil since it will think your package is newwer then ANY upgraded package unless the upgraded package has an epoch yours. The --revision flag in kernel-package only makes an epoch if you explicitly