Comment 2 for bug 439406

Being able to enable/disable an archive permission instead of being restricted to just adding/removing allows one to maintain the permission list for an archive while still being able to disable those permissions. An example use case would be a project is using a PPA that has a period of code freeze around releases where it would be desirable to prevent uploads from all or just certain users/teams. After the code freeze, we'd currently have to recreate the archive permissions which will require maintaining that data elsewhere for the duration of freeze. It would be less error prone, less overhead, and reduce the need for any resources to store that data while it exists outside of launchpad if that information never had to exist outside of launchpad which would be possible if permissions could be toggled between enabled/disabled.