On Wed, May 19, 2010 at 7:07 AM, Jeremy Evans <[email protected]>wrote:
> On May 19, 6:10 am, Scott LaBounty <[email protected]> wrote: > > I just got a new machine after my old one died and I'm rebuilding pretty > > much everything from scratch. I installed sequel ("sudo gem install > sequel") > > and all of my test scripts seem to still work. The only thing is that I > > can't do a "sequel --version" which probably means no migrations also. I > > don't remember having to do anything to the PATH last time around, but > > obviously, I could be (and probably am) wrong. sequel does show up in > > /var/lib/gems/1.9.1/gems/sequel-3.11.0/bin/sequel. > > > > Any thoughts? > > Try running > > which sequel > > That should give you the path to bin/sequel if it is installed, or an > error message otherwise. Based on your post, you'll probably get an > error message, so you'll have to add the bin/sequel rubygems stub to > your PATH manually. > > Jeremy > > -- > You received this message because you are subscribed to the Google Groups > "sequel-talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<sequel-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/sequel-talk?hl=en. > > Thanks Jeremy. I had already done the "which sequel" and it wasn't found. I'll just put a sym link in /usr/bin. I just don't recall having to do this before. It looks like I have the same issue with ramaze also. Anyone know if this used to be part of the installation process that got removed? -- Scott http://steamcode.blogspot.com/ -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
