El 21/07/14 14:09, JezC escribió:
> Hi Ignacio
> 
> I'm pretty sure that part of the issue is the repository layout.
> 
> When I look at the Rails repo, I see that the top level includes a
> gemspec. I think that's what makes rails work with a "gem 'rails',
> '4.0.8'" rather than having to call out each component - I tried
> tinkering with my hobo fork to see if I could make it work, and without
> a top level gemspec, I think we *HAVE* to mention each chunk. I'm
> currently playing with a branch of dependencies in my fork, to see if I
> can make a Rails-like master gemspec, that, when included, calls the
> other stuff. 

Perfect, please send a pull request if you find a working setup :)


> 
> Cheers, JeremyC.
> 
> On Monday, 21 July 2014 11:04:39 UTC+1, Ignacio Huerta wrote:
> 
>     Hi Jeremy,
> 
>     El 18/07/14 12:16, JezC escribió:
>     > Updating from Hobo 2.1.0 to 2.1.1 I realised that the default Gemfile
>     > created by "hobo new" does something I don't understand.
>     >
>     > The generated Gemfile includes:
>     >
>     > gem 'hobo', '2.1.0'
>     > gem "hobo_will_paginate"
>     > gem "hobo_bootstrap", "2.1.0"
>     > gem "hobo_jquery_ui", "2.1.0"
>     > gem "hobo_bootstrap_ui", "2.1.0"
>     > gem 'jquery-ui-themse', "~> 0.0.4"
>     > gem"hobo_clean_admin", "2.1.0"
>     >
>     > Why do we need to include the hobo components, locked to a
>     specific rev
>     > level? I think we can replace these multiple lines with just:
>     >
>     > gem 'hobo', '2.1.1'
>     > gem 'protected_attributes'
>     > gem 'jquery-ui-themes', '~> 0.0.4'
>     >
>     > AFAICS, asking for hobo 2.1.1 will result in the hobo_bootstrap, etc
>     > gems being included, at the right rev level?
> 
>     Yes, I'm 99,5% sure that including the specific components is not
>     necessary, just a legacy. But I'd like to test it a bit more before
>     changing the generators, because I believe that you need to include one
>     of "hobo_clean" or "hobo_bootstrap" for the templates to work. I'll add
>     an issue to check this.
> 
> 
>     >
>     > We do need the protected_attributes gem, I think - a consequence of
>     > hobo_model?
> 
>     Yes, this allows the usage of "Rails 3.2" style of protecting
>     attributes, instead of the Rails 4 "strong parameters" version. It
>     seems
>     like the best fit for Hobo.
> 
>     >
>     > And we probably want to specify a minimum rev for the
>     jquery_ui_themes.
>     >
>     > Saves locking rev levels of some entities that should be dependent
>     on a
>     > primary gem's rev level.  I can't think of a plausible common
>     scenario
>     > to ask for an older rev of one of these components?
> 
>     Apart from the possibility of using a different template, no, I
>     think we
>     can clean up the Gemfile :).
> 
>     Regards,
>     Ignacio
> 
>     >
>     > Cheers, JeremyC
>     >
>     > On Thursday, 17 July 2014 18:09:50 UTC+1, Ignacio Huerta wrote:
>     >
>     >     Hi everyone!
>     >
>     >     This afternoon I could wait no more and I found the source of
>     >     compatibility issue since Rails 4.0.6. It turns out Rails has
>     renamed a
>     >     method in ActiveRecord, a method Hobo is using
>     >    
>     
> (https://github.com/Hobo/hobo/commit/4779ce605bd6627e2fba7a98ddd708c5d3167aba
>     
> <https://github.com/Hobo/hobo/commit/4779ce605bd6627e2fba7a98ddd708c5d3167aba>
> 
>     >    
>     
> <https://github.com/Hobo/hobo/commit/4779ce605bd6627e2fba7a98ddd708c5d3167aba
>     
> <https://github.com/Hobo/hobo/commit/4779ce605bd6627e2fba7a98ddd708c5d3167aba>>).
> 
>     >
>     >
>     >     The good news is that Hobo 2.1.1 has been released, tested
>     with Ruby
>     >     2.1
>     >     and Rails 4.0.8. I will be very grateful if you can install
>     and test it
>     >     a bit more :).
>     >
>     >     I want to say special thanks to committers since last release:
>     >
>     >       Peter Savichev (https://github.com/proton)
>     >       Paul (https://github.com/tacid)
>     >       Tim Griffin (https://github.com/enwood)
>     >
>     >     And also thanks to all the people using Hobo and reporting
>     issues and
>     >     ideas. It's a pleasure to develop with you!
>     >
>     >     Warm regards,
>     >     Ignacio
>     >
>     > --
>     > You received this message because you are subscribed to the Google
>     > Groups "Hobo Users" group.
>     > To unsubscribe from this group and stop receiving emails from it,
>     send
>     > an email to [email protected] <javascript:>
>     > <mailto:[email protected] <javascript:>>.
>     > To post to this group, send email to [email protected]
>     <javascript:>
>     > <mailto:[email protected] <javascript:>>.
>     > Visit this group at http://groups.google.com/group/hobousers
>     <http://groups.google.com/group/hobousers>.
>     > For more options, visit https://groups.google.com/d/optout
>     <https://groups.google.com/d/optout>.
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Hobo Users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected]
> <mailto:[email protected]>.
> To post to this group, send email to [email protected]
> <mailto:[email protected]>.
> Visit this group at http://groups.google.com/group/hobousers.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/d/optout.

Reply via email to