[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

handling rails-assets as a virtual file system (Re: namespace conflicts in rails generators)



On Wednesday 26 November 2014 07:50 PM, Antonio Terceiro wrote:
> the same way we solve the issue with rails engines. I won't have much
> motivation to work on that, however, before jessie is out.

> If anyone wants to give it a try, I just pushed my WIP tree to alioth,
> under the `install-as-gem` branch.
> 

how about we create a virtual file system like /proc for rails assets?
So if an application requires rails-assets-jqury-ui, it can just require
rails-assets and libjs-jqury-ui. Rails assets virtual file system will
return the necessary gemspec files for installed javascripts if there is
a bower json file present. This will reduce the number of packages we
have to maintain significantly. rails-assets.org itself is using a proxy
to serve rubygems.

I think we can offer this as a google summer of code project. What does
everyone think about it?

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: