How much work would it be to include OpenSSL? Do people find this useful?
For me it would make SFTP available out of the box.
Thoughts?
--
Jos Backus _/ _/_/_/ Sunnyvale, CA
_/ _/ _/
_/ _/_/_/
_/ _/ _/ _/
jos at catnook.com _/_/ _/_/_/ require
''std/disclaimer''
On Thu, 2004-07-29 at 19:12, Jos Backus wrote:> How much work would it be to include OpenSSL? Do people find this useful? > For me it would make SFTP available out of the box.IIRC, the problem is legal, not technical. There are potential problems with distributing SSL code in certain jurisdictions, and I didn''t want to get involved in any nastiness. If I''m wrong, then by all means I think it should be included. But as I recall, there are issues... thanks. /\ndy
Andrew Hunt wrote:> > On Thu, 2004-07-29 at 19:12, Jos Backus wrote: > > How much work would it be to include OpenSSL? Do people find > this useful? > > For me it would make SFTP available out of the box. > > IIRC, the problem is legal, not technical. There are potential problems > with distributing SSL code in certain jurisdictions, and I didn''t want > to get involved in any nastiness. > > If I''m wrong, then by all means I think it should be included. But as I > recall, there are issues...Rich Kilmer and Chad Fowler are busy creating a GUI interface for RubyGems which I want to include in the installer (and possibly automatically invoke) to allow the user to install additional packages of their choice. Rich has promised me to have this ready within the next week or so. If someone (you?) could package up OpenSSL as a gem, then it could be easily installed by any user who wanted it (and we don''t have to worry about any legal issues). Curt
On Thu, Jul 29, 2004 at 07:02:48PM -0500, Curt Hibbs wrote:> Andrew Hunt wrote: > > > > On Thu, 2004-07-29 at 19:12, Jos Backus wrote: > > > How much work would it be to include OpenSSL? Do people find > > this useful? > > > For me it would make SFTP available out of the box. > > > > IIRC, the problem is legal, not technical. There are potential problems > > with distributing SSL code in certain jurisdictions, and I didn''t want > > to get involved in any nastiness. > > > > If I''m wrong, then by all means I think it should be included. But as I > > recall, there are issues... > > Rich Kilmer and Chad Fowler are busy creating a GUI interface for RubyGems > which I want to include in the installer (and possibly automatically invoke) > to allow the user to install additional packages of their choice. Rich has > promised me to have this ready within the next week or so.Cool.> If someone (you?) could package up OpenSSL as a gem, then it could be easily > installed by any user who wanted it (and we don''t have to worry about any > legal issues).Okay, I''ll look into this. Does the gem format support binary files (DLLs)? I haven''t looked into RubyGems yet, sorry. Time to do some reading. Jos> Curt-- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos at catnook.com _/_/ _/_/_/ require ''std/disclaimer''
Jos Backus wrote:> > On Thu, Jul 29, 2004 at 07:02:48PM -0500, Curt Hibbs wrote: > > > > Rich Kilmer and Chad Fowler are busy creating a GUI interface > for RubyGems > > which I want to include in the installer (and possibly > automatically invoke) > > to allow the user to install additional packages of their > choice. Rich has > > promised me to have this ready within the next week or so. > > Cool. > > > If someone (you?) could package up OpenSSL as a gem, then it > could be easily > > installed by any user who wanted it (and we don''t have to worry > about any > > legal issues). > > Okay, I''ll look into this. Does the gem format support binary > files (DLLs)? I > haven''t looked into RubyGems yet, sorry. Time to do some reading.It *does* support binary gems, but improved support is coming very soon. Right now you can package up a binary gem for each platform, but the user has to choose the correct version. Rich and Chad are also working to extend it so that you just pick what package you want, and RubyGems will choose the correct binary package for your platform. Curt
On Fri, Jul 30, 2004 at 07:45:50AM -0500, Curt Hibbs wrote:> It *does* support binary gems, but improved support is coming very soon. > Right now you can package up a binary gem for each platform, but the user > has to choose the correct version. Rich and Chad are also working to extend > it so that you just pick what package you want, and RubyGems will choose the > correct binary package for your platform.Great. So it boils down to: - Build OpenSSL - Install it to some location - Package up the bits in that location using a gemspec. I take it I can just copy what (say) FXRuby does. Sound okay? -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos at catnook.com _/_/ _/_/_/ require ''std/disclaimer''
Jos Backus wrote:> > On Fri, Jul 30, 2004 at 07:45:50AM -0500, Curt Hibbs wrote: > > It *does* support binary gems, but improved support is coming very soon. > > Right now you can package up a binary gem for each platform, > but the user > > has to choose the correct version. Rich and Chad are also > working to extend > > it so that you just pick what package you want, and RubyGems > will choose the > > correct binary package for your platform. > > Great. So it boils down to: > - Build OpenSSL > - Install it to some location > - Package up the bits in that location using a gemspec. I take it > I can just > copy what (say) FXRuby does.I think that is basically it (coming from someone who has not yet created a RubyGem, either). You might also want to read through the getting started material on the RubyGems site. Also, I would contact the authors ruby-openssl and let then know you are doing this. And finally, since openssl is not a RubyForge project, and since RubyForge the primary (or only) public RubyGems server, you need to find out how to get your gem in the RubyForge repository (I cc''d Tom Copeland for an answer on this). Or maybe in your contacts with the authors, the prospect of getting an easily installed gem version might convince them to move to RubyForge! You can always suggest this. The advantage to being a RubyForge project, is that you merely have to release the gem file on the RubyForge project and it automatically goes into the gem server repository. Curt
On Fri, Jul 30, 2004 at 11:58:31AM -0500, Curt Hibbs wrote:> Jos Backus wrote: > > Great. So it boils down to: > > - Build OpenSSL > > - Install it to some location > > - Package up the bits in that location using a gemspec. I take it > > I can just > > copy what (say) FXRuby does. > > I think that is basically it (coming from someone who has not yet created a > RubyGem, either). You might also want to read through the getting started > material on the RubyGems site.Yeah, I read all the material there last night. Found one typo: one wiki page refers to gem_path as the config keyword whereas others refer to it as gempath. I would prefer to use underscores (plus there''s GEM_PATH already). Not sure yet what the actual software uses.> Also, I would contact the authors ruby-openssl and let then know you are > doing this.Okay.> And finally, since openssl is not a RubyForge project, and since RubyForge > the primary (or only) public RubyGems server, you need to find out how to > get your gem in the RubyForge repository (I cc''d Tom Copeland for an answer > on this). > > Or maybe in your contacts with the authors, the prospect of getting an > easily installed gem version might convince them to move to RubyForge! You > can always suggest this. The advantage to being a RubyForge project, is that > you merely have to release the gem file on the RubyForge project and it > automatically goes into the gem server repository.That sounds really convenient indeed. Hope you enjoy your vacation, Curt! Cheers, -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos at catnook.com _/_/ _/_/_/ require ''std/disclaimer''