Thanks, I just forwarded this onto epel-devel w/ some appropriate
context. Will see what the response is before starting.
On 06/15/2015 09:34 AM, Troy Dawson wrote:
Sorry for the late reply, but you didn't mention which EPEL you were
EPEL5,6 or 7?
And in reality, this is the wrong list to be asking/stating that.
You need to talk about it on the EPEL list.
On this list, everyone is excited to get rails updated. On the EPEL
list, you'll find out who you are going to break.
On 06/12/2015 09:28 AM, Mo Morsi wrote:
> I've done some investigation as to updating rails in EPEL to the latest
> release (4.2.1).
> As part of this I've been refactoring polisher  and have written a
> few new utilities to cross reference upstream / downstream dependencies
> and output the results in in a tree like manner  as well as to
> highlight upstream dependencies missing downstream .
> The results of the last utility run  should give a rough estimate of
> the work entailed. Dev deps have been included for this run so many
> updates are duplicate / unecessary.
> I'll look into consolidating this list and taking some of the simpler
> updates in the near future, obviously the more eyeballs that we get on
> this, the quicker it will go.
>  https://github.com/ManageIQ/polisher
>  https://github.com/ManageIQ/polisher/blob/master/bin/gem_mapper.rb
>  https://mmorsi.fedorapeople.org/gem_mapper.png
>  https://github.com/ManageIQ/polisher/blob/master/bin/missing_deps.rb
>  https://mmorsi.fedorapeople.org/missing_deps_output
> ruby-sig mailing list
ruby-sig mailing list