Changes between Version 2 and Version 3 of Ticket #56, comment 1
- Timestamp:
- May 19, 2013, 5:43:09 AM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #56, comment 1
v2 v3 1 I've been meaning to suggest something a bit similar ... A ''withdrawn'' notification ... Sometimes a pack becomes outdated, unnecessary or gets merged with other packages and is no longer supported and may even cause incompatabilities if it stays ... If possible when a package is removed .. (depot page deleted or package number becomes unavailable or a package is unpublished .. 1 of these) the user gets a notification that this package d has been withdrawn and maybe ask them if they'd like to delete it (on condition he has it downloaded in the first place)1 I've been meaning to suggest something a bit similar ... A ''withdrawn'' notification ... Sometimes a pack becomes outdated, unnecessary or gets merged with other packages and is no longer supported and may even cause incompatabilities if it stays ... If possible when a package is removed .. (depot page deleted or package number becomes unavailable or a package is unpublished .. 1 of these) the user gets a notification that this package has been withdrawn and maybe ask him if he'd like to delete it (on condition he has it downloaded in the first place) 2 2 This can be extended for what iritscen is saying .. The package is withdrawn .. User gets notified to remove it ... And then it can be reintroduced with a different number or node page or whatever. 3 3 Also maybe AEI can take the depot page number as reference to identify mods instead of the package number field .. Since deleting nod pages is now restricted to the moderators there's less chance that the nod page number would change than a package number change..
