From: Roy Wright <royw@cisco.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ruby gems vs. ebuilds
Date: Thu, 05 Oct 2006 16:03:51 -0500 [thread overview]
Message-ID: <45257337.4080802@cisco.com> (raw)
In-Reply-To: <97c95c3d0610051316y4577bf75tb14ddd70799b4824@mail.gmail.com>
Boris Fersing wrote:
>
>
> AFAIK, the ruby related ebuilds use gem. For example rails has in his
> ebuild :
>
> "inherit ruby gems"
>
> and if you look in the gems eclass :
>
> [snip]
> And it's the same for rake !
>
> The problem might be (that's a supposition only) that gem installs the
> files in the image which will be merged to the system by portage and
> doesn't install the files directly in the "real" system.
>
> or maybe did I miss something ?
>
I stand corrected on the ebuilds. I looked at another of my systems that
did not show the problem but had both rake gem and ebuild installed.
I'm wondering if it is something to do with "gem update". I've been
running two systems in parallel, one for development, one for production.
The development system is running testing (~x86) while production system
is running stable (x86). The development system is updated daily, the
production about once a month. During my recent rails web app
development I've been careful to install the same gems at the same
time on both systems. I also did a "gem update" on both system about
a day before I noticed the problem on my production system.
I verified that gem and portage are playing with the same version
rake-0.7.1. Then I re-emerged rake on the production system.
Running: rake --tasks in the application directory gives this:
cowboy current # rake --tasks
(in /var/rails/rodeo/releases/20061005042627)
/usr/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/validations.rb:334:
warning: `*' interpreted as argument prefix
/usr/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/validations.rb:363:
warning: `*' interpreted as argument prefix
/usr/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/migration.rb:224:
warning: instance variable @ignore_new_methods not initialized
/usr/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/migration.rb:224:
warning: instance variable @ignore_new_methods not initialized
/usr/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/connection_adapters/abstract/connection_specification.rb:41:
warning: method redefined; discarding old allow_concurrency=
/usr/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/connection_adapters/sqlserver_adapter.rb:456:
warning: method redefined; discarding old remove_column
/usr/lib/ruby/gems/1.8/gems/activerecord-1.14.4/lib/active_record/connection_adapters/oracle_adapter.rb:119:
warning: (...) interpreted as grouped expression
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/request.rb:171:
warning: method redefined; discarding old relative_url_root
/usr/lib/ruby/1.8/cgi/session/pstore.rb:17: warning: method redefined;
discarding old []=
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_ext/raw_post_data_fix.rb:57:
warning: ambiguous first argument; put parentheses or even spaces
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/cgi_ext/raw_post_data_fix.rb:8:
warning: method redefined; discarding old initialize_query
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session/active_record_store.rb:129:
warning: private attribute?
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_controller/session/active_record_store.rb:179:
warning: method redefined; discarding old connection
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_view/helpers/prototype_helper.rb:641:
warning: ambiguous first argument; put parentheses or even spaces
/usr/lib/ruby/gems/1.8/gems/actionpack-1.12.5/lib/action_view/helpers/prototype_helper.rb:874:
warning: `*' interpreted as argument prefix
/usr/lib/ruby/gems/1.8/gems/actionmailer-1.2.5/lib/action_mailer/vendor/tmail/facade.rb:486:
warning: method redefined; discarding old create_reply
/usr/lib/ruby/gems/1.8/gems/actionwebservice-1.1.6/lib/action_web_service/protocol/xmlrpc_protocol.rb:6:
warning: discarding old message
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:581: warning:
method redefined; discarding old []=
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:590: warning:
method redefined; discarding old []
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:595: warning:
method redefined; discarding old keys
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:600: warning:
method redefined; discarding old find_pair
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:607: warning:
method redefined; discarding old []=
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:611: warning:
method redefined; discarding old []
/usr/lib/ruby/gems/1.8/gems/rails-1.1.6/lib/initializer.rb:615: warning:
method redefined; discarding old method_missing
rake backgroundrb:remove # Remove backgroundrb from your
rails application
[snip]
unmerging rake, then installing rake via gem solves the problem:
cowboy current # emerge --unmerge rake
[snip]
cowboy current # gem install rake -r
Attempting remote installation of 'rake'
Successfully installed rake-0.7.1
Installing RDoc documentation for rake-0.7.1...
cowboy current # rake --tasks
(in /var/rails/rodeo/releases/20061005042627)
rake backgroundrb:remove # Remove backgroundrb from your
rails application
[snip]
So something is different between the ebuild and manual gem installs...
Sorry, I didn't mean to take this thread into what belongs on bugzilla.
I was more curious
on the philosophy on why duplicate the gems as ebuilds? But I'm
thinking now it is probably
to allow gems to be dependencies of applications in portage.
Thank you,
Roy
--
echo "spzxAdjtdp/dpn" | perl -pe 's/(.)/chr(ord($1)-1)/ge'
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2006-10-05 21:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-05 20:03 [gentoo-dev] ruby gems vs. ebuilds Roy Wright
2006-10-05 20:16 ` Boris Fersing
2006-10-05 21:03 ` Roy Wright [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45257337.4080802@cisco.com \
--to=royw@cisco.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox