$ gem install *.gem should do topo sort #108

Closed
zenspider opened this Issue Jun 14, 2011 · 3 comments

Comments

Projects
None yet
6 participants
@zenspider
Contributor

zenspider commented Jun 14, 2011

At least, I've had hints that it doesn't... we don't have a test for it, that's for sure.

From: http://rubyforge.org/tracker/index.php?func=detail&aid=29231&group_id=126&atid=578

@ghost ghost assigned zenspider Jun 14, 2011

@spastorino

This comment has been minimized.

Show comment Hide comment

nobu pushed a commit to nobu/rubygems that referenced this issue Jan 12, 2014

Merge pull request #108 from BanzaiMan/zlib_gzipreader_external_encoding
1.9 added option to specify external encoding to Zlib::GzipReader#read

@krainboltgreene krainboltgreene removed this from the Unfulfilled Promises and Broken Dreams milestone Jan 1, 2016

@krainboltgreene krainboltgreene changed the title from gem install *.gem should do topo sort to $ gem install *.gem should do topo sort Jan 1, 2016

@copiousfreetime

This comment has been minimized.

Show comment Hide comment
@copiousfreetime

copiousfreetime Jan 18, 2016

Contributor

This appears to still be an issue. When doing an installation of multiple gems on the command line, the gems are individually installed in isolation. The set of all gems on the command line is not aggregated into a single installation set.

It looks like this could be implemented by updating InstallCommand#install_gems to create a Gem::RequestSet and installing in the same manner as #install_from_gemdeps.

In general, I think this issue is a consolidation of all the inputs to installation and a normalization of them to use a RequestSet.

We would need to make sure we still support ignoring dependendencies.

Contributor

copiousfreetime commented Jan 18, 2016

This appears to still be an issue. When doing an installation of multiple gems on the command line, the gems are individually installed in isolation. The set of all gems on the command line is not aggregated into a single installation set.

It looks like this could be implemented by updating InstallCommand#install_gems to create a Gem::RequestSet and installing in the same manner as #install_from_gemdeps.

In general, I think this issue is a consolidation of all the inputs to installation and a normalization of them to use a RequestSet.

We would need to make sure we still support ignoring dependendencies.

@bronzdoc

This comment has been minimized.

Show comment Hide comment
@bronzdoc

bronzdoc Mar 31, 2018

Member

This has been ide for too long i'm going to close it, if still interested please let us know in a new issue.

Member

bronzdoc commented Mar 31, 2018

This has been ide for too long i'm going to close it, if still interested please let us know in a new issue.

@bronzdoc bronzdoc closed this Mar 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment