Re: Ruby on Rails and pkgsrc
On 2006-03-18, Petr Janda <[EMAIL PROTECTED]> wrote: > Im planning to learn Ruby, and I want to setup Apache2, MySQL and Ruby on=20 > Rails, but I cannot find a rails port in pkgsrc. Is there one actually? Just install misc/rubygems (ruby's own component management infrastructure) from pkgsrc and then do a "gem install rails". Regards, Csaba
Re: Ruby on Rails and pkgsrc
> > Im planning to learn Ruby, and I want to setup Apache2, MySQL and Ruby on=20 > > Rails, but I cannot find a rails port in pkgsrc. Is there one actually? > > Just install misc/rubygems (ruby's own component management > infrastructure) from pkgsrc and then do a "gem install rails". Does this provide a way to uninstall? And does this provide a way to manage the installed files (such as pkg_info, pkg_delete)? Anyone interested in packaging this? Jeremy C. Reed echo ':6DB6=88>?;@69876tA=AC8BB5tA6487><' | tr '4-F' 'wu rofIn.lkigemca'
Re: Ruby on Rails and pkgsrc
On 2006-03-18, Jeremy C. Reed <[EMAIL PROTECTED]> wrote: >> Just install misc/rubygems (ruby's own component management >> infrastructure) from pkgsrc and then do a "gem install rails". > > Does this provide a way to uninstall? And does this provide a way to > manage the installed files (such as pkg_info, pkg_delete)? Yes, gems intend to be a full fledged package management system, see "gem help commands" for a quick summary. > Anyone interested in packaging this? FYI, there is the FreeBSD way: you can find the port "rubygem-rails" (and some other rubygem-* ports), which integrates the gem installation into the port installation / package database. While there are benefits of this approach, this requires separate package maintainance for each rubygem-* port, and I'm not sure that it's worth for the effort. (Given that files won't go wild under gem control and that those ruby extensions on which non-ruby stuff depend do/will have a dedicated port/package nevertheless.) I'd say it would make sense to gather some experience about the Dfly + pkgsrc + rubygems combo before looking for alternatives :) (I haven't tried this myself, so I can't say it will work like a charm.) Regards, Csaba
Re: Ruby on Rails and pkgsrc
At 7:27 AM -0800 3/18/06, Jeremy C. Reed wrote: > > Im planning to learn Ruby, and I want to setup Apache2, > > MySQL and Ruby on Rails, but I cannot find a rails port > > in pkgsrc. Is there one actually? > Just install misc/rubygems (ruby's own component management infrastructure) from pkgsrc and then do a "gem install rails". Does this provide a way to uninstall? And does this provide a way to manage the installed files (such as pkg_info, pkg_delete)? Anyone interested in packaging this? The gems package-management system provides features that other OS-based package-management systems do not provide. That's mainly because developers in the ruby community expect to use gems to distribute their package. Thus, the *original* developer will create and support the gem for their package, instead of having some "ports-team developer" constantly chasing after a package, and re-working the build environment so that package will build on the target OS. OS-specific ports teams are *constantly* playing catch-up with whatever the original developers are releasing. Among other things that gems provides is a way to handle multiple versions of the same package installed at the same time. Ruby scripts can specify which versions of some package that they will work with, and the same OS can easily support different scripts which "must have" incompatible versions of a given gem. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED]
Re: Ruby on Rails and pkgsrc
On Mon, 20 Mar 2006, Garance A Drosihn wrote: > Among other things that gems provides is a way to handle > multiple versions of the same package installed at the > same time. Ruby scripts can specify which versions of > some package that they will work with, and the same OS > can easily support different scripts which "must have" > incompatible versions of a given gem. Just want to mention that pkgsrc provides a feature like this also also -- where multiple versions of same package can be installed at same time. It is not well tested (and not all packages have been checked), but I have used it some myself. Jeremy C. Reed echo '9,J8HD,[EMAIL PROTECTED]:[EMAIL PROTECTED];[EMAIL PROTECTED]@5GBIELD54DL>@8L?:5GDEJ8LDG1' |\ sed ss,s50EBsg | tr 0-M 'p.wBt SgiIlxmLhan:o,erDsduv/cyP'
Re: Ruby on Rails and pkgsrc
At 8:19 AM -0800 3/20/06, Jeremy C. Reed wrote: On Mon, 20 Mar 2006, Garance A Drosihn wrote: Among other things that gems provides is a way to handle multiple versions of the same package installed at the same time. Ruby scripts can specify which versions of some package that they will work with, and the same OS can easily support different scripts which "must have" incompatible versions of a given gem. Just want to mention that pkgsrc provides a feature like this also also -- where multiple versions of same package can be installed at same time. It is not well tested (and not all packages have been checked), but I have used it some myself. I'm not saying anyone should abandon pkgsrc for managing other packages, since the vast vast majority of packages have absolutely nothing to do with ruby. But I would not abandon ruby-gems only to spend a lot of time and effort trying to re-package every single gem in some other form. That is a lot of duplicated effort on an ongoing basis, and I'm sure that much effort would see much higher rewards if spent on other areas. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED]
