[openbeos] Re: SVN in Haiku

Ingo Weinhold wrote:
I'm all for a common place where ported applications or libraries are available in source and compiled form -- a revived GeekGadgets, if you want. I just don't think the Haiku repository should be that place. Something like http://tools.assembla.com/BePorts/ looks promising to me, though.
(This is my last word on the subject; like I said I really don't intend to argue about this because I'm not on the dev team, and this is a fundamental difference of opinion on project management, of which I'm no expert. :-) )
I understand and agree that there are many libraries and apps out there that shouldn't be included in the Haiku repository, but OpenSSL is such a significant library in open source and closed source projects, and its use is pretty much a standard across the open source community that it seems logical that it would be included as part of the OS these days instead of added on by developers and users.
Along similar lines, zlib is also a commonly used library and it is in the Haiku repository. There may very well be multiple reasons why zlib is included as part of a Haiku build, not the least of which are the gzip and other commandline tools that use it, but is not SSL the basis for ssh, STARTTLS in the POP3 mail retrieval protocol, and HTTPS? It seems reasonable to me that it should be inlcuded in the OS.
As for the possible argument that Be didn't include it in R5, I agree it wasn't and I believe that was a flaw in R5. Be did include it in library only form with a later version of NetPositive that was released (or at least intended to be released; I can't recall if it was or not, but I remember Chris Tate working on it) when the SSL library that it had been using went away or the license expired. (I can't remember which.) If I remember correctly, the final version of BONE was also supposed to include the OpenSSL headers and libraries. So the precedent of including in the OS is there, and not just with the Linux/BSD communities. That should count for something... :-) 

Now, as I said, I will not speak of this again. (For now at least. ;-) )
Raymond

--
Raymond C. Rodgers
http://www.raymondrodgers.com/

Other related posts: