Cristian Rodríguez wrote:
Linda Walsh escribió:
Where would I find the suse 11.0 pre-release source packages?
Am looking to upgrade my "open-ssh" to 4.7 and am hoping it's already in the 11.x tree -- I have a patch for high-speed ssh, that applies
If you do so, you need to recompile openSSH, and possible other components, I strongly suggest you not to do that, messing with applications that contains crypto code can become **very** tricky.
At SUSE, people avoid doing such things, for very good reasons, even those who have extensive knowledge in the area.
You have been warned ;-P
Did you not understand what I was trying to do? Or, I guess I don't understand why you are trying to warn me away from doing what is done in the linux open-source world all the time. I am not CR, but I'm not sure you understood his warning.
I said I was downloading a *source* package, so it's seems like knowing that one has to build from source is a given -- yet you warn about the need to 'recompile' openssh? That's a bit confusing. I believe his warning isn't so much just the need to rebuild openssh, it is that there are many OTHER packages that are built against the
On 05/23/2008 06:23 AM, Linda Walsh wrote: libraries in openssh, which all may need to be rebuilt against the newer version of openssh. It can be a dependency nightmare of sorts.
I also mentioned that I had a patch (standard linux patch composed of the output of "diff -u") that I needed to apply to a version, *higher* than the one included in 10.3. The patch for High performance scp/ssh is from: "http://www.psc.edu/networking/projects/hpn-ssh/".
Did you not understand? I.e. -- you seemed to be warning me away from rebuilding openssh -- which I would think would be required for any patch to be applied. Am I missing something or was I unclear about what I was trying to do?
I think you are missing how many other programs use openssh and link against its libraries. Changing it may mean rebuilding a lot of other programs, which may rebuild with the newer openssh, or may introduce problems related to a newer version.
Am not sure why you would be pushing customers away from building their own versions of packages that they need for their systems. Isn't that one of the main 'selling points' of Open Source?
This is true, but replacing a brick at the foundation is a lot more different than one at the top.
If you could explain your concerns (or were you trying to be humorous and I missed the ":-)" ), as your concerns seem confusing for someone working at an open-source distribution company (I wouldn't find it so surprising coming from someone a closed or proprietary software company like microsoft, but SuSE ain't them...:-)).
I can only guess at what CR was implying, but I believe I understood him correctly. It isn't that it cannot be done, but openssh, openssl, etc. are used in a lot of other packages. I have attempted similar things in the past and can understand what he is warning about, i.e. you want a newer <?>, but 10 package need xxx.so.1, but the newer has xxx.so.2, and all 10 packages now need to be rebuilt, but even after rebuilding (assuming they all rebuild), there is strangeness that wasn't there previously, and now you need to figure out if it is the relation between one of the 10 to the new library, or the new library itself, etc. It isn't trivial. It can be done, but it takes work, and thus his warning. HTH. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org