rubygems / new-index

Prototype and documentation of the new gem index format
12 stars 2 forks source link

Yanking all versions of a gem? #1

Closed marshally closed 9 years ago

marshally commented 10 years ago

New index format looks neat!

Question:

In the case of all versions of a gem being yanked, and someone taking the namespace for a different gem: http://help.rubygems.org/kb/gemcutter/removing-a-published-rubygem

Will this cause the ETag check to fail and therefore bundler re-downloads the appropriate files?

Marshall

indirect commented 10 years ago

Yup, that's exactly why the rtag check exists. That same check also protects against transmission errors and allows us to rewrite the versions list occasionally, consolidating all versions of a single gem down to one line.

On Thu, Mar 20, 2014 at 10:02 AM, Marshall Yount notifications@github.com wrote:

New index format looks neat! Question: In the case of all versions of a gem being yanked, and someone taking the namespace for a different gem: http://help.rubygems.org/kb/gemcutter/removing-a-published-rubygem Will this cause the ETag check to fail and therefore bundler re-downloads the appropriate files?

Marshall

Reply to this email directly or view it on GitHub: https://github.com/bundler/new-index/issues/1