[Rubygems-developers] gem lock

Trans transfire at gmail.com
Wed Sep 29 17:28:58 EDT 2010


On Sep 29, 3:19 pm, Luis Lavena <luislav... at gmail.com> wrote:
> On Wed, Sep 29, 2010 at 6:12 AM, Trans <transf... at gmail.com> wrote:
> > I recently noticed that `gem` had a `lock` command. I played around
> > with it and found it mostly useless. First, one has to provide it the
> > name and version of an installed gem. It would be much more useful if
> > it could take a gemspec file instead. Also, it does not appear to
> > utilize remote gem source(s) to resolve best dependencies, but simply
> > uses the versions of gems installed locally. It would be much more
> > useful if it recognized the --remote option and acted accordingly.
> > Also, it could use an option to include/not-include development
> > dependencies.
>
> I actually don't remember the last time I used that command and
> discarded by ~> in my gem dependencies
>
> Do we have a 1.4.x Roadmap? If not, this for sure can be removed then.

Why remove it? Why not just fix it?


More information about the Rubygems-developers mailing list