Feature Requests: Browse | Submit New | Admin

[#2466] Delete gems from the repository when they are deleted from a project's files page

Date:
2005-09-15 09:08
Priority:
3
Submitted By:
Doug Kearns (dkearns)
Assigned To:
Nobody (None)
Category:
None
State:
Open
Summary:
Delete gems from the repository when they are deleted from a project's files page

Detailed description
While the current integration of the gems repository and rubyforge is great it would also be useful if gems deleted,
or made inactive, in a project's released file list were also deleted from the repository.

Add A Comment: Notepad

Please login


Followup

Message
Date: 2006-11-25 03:32
Sender: Tom Copeland

More comments from Dan Berger:

I generally don't like to delete old releases.  I like to keep
them around just in case I need to rollback, or someone
happens to need an old version for compatibility reasons.

However, I don't want to keep the old gems indexed.  When doing
a remote gem install it can get annoying to see the
slew of old gems listed along with the current gems.

Thus, when a user marks a release as "hidden", I would
prefer it if the gem for that release would automatically
be removed from the gem index.  That way users won't be annoyed
by a really long list of old gems when they do a remote
gem install, but could still download and build the gem manually
if they ever needed to.

I suppose the inverse should work as well, i.e. if a hidden release
is marked active, any gem files should be added
back to the index.

Attached Files:

Name Description Download
No Files Currently Attached

Changes:

No Changes Have Been Made to This Item