On Mon, Sep 11, 2000 at 10:18:28PM -0700, Kastus wrote:
I wonder why some SuSE users expect that every of 1000+ packages to changed their versions between 6.4 and 7.0. It's a free world, nobody prevents one from grabbing open source and compile himself. SuSE doesn't have to have all bleeding edge versions.
-Kastus
<Flame> LOOK - I was providing a suggestion for the fine folks at SuSE to enhance their product offering. The 7.0 packages are of little value to anyone who is not running 7.0. Nowhere did I demand (or even ask) that they compile the bleeding edge openssh version for their distro. What I DID ask was they put the version of the crypto software that they have already compiled and burned onto a CD on their website. Because of the silly US crypto laws I cannot get that software on the CD I buy from SuSE. SuSE, in the persona of Ben Rosenberg, understands this. Because I am not on the SuSE development team I do not know if any old versions of specific packages are compatible with the current distribution. What I do know is the version that ships on the non-US CD's most likely works, and the old versions may or may not work. I'm not asking SuSE to compile squat, just copy a file to their FTP site a few weeks in advance. And if you'd read my original post, you'd see that I had listed compiling my own version as an option. However, there are some people out there that might think twice about compiling their own security software. While I have done so in the past (including ssh and openssh) I'd prefer to use the vendor suppplied supported version. Where's the big surprise with that? The whole purpose of my original post was to give SuSE a way to improve their customer support and usability, NOT to flame them. </Flame> Yours truly, Andrew Diederich -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq