The overwhelming majority of people don't need old versions floating about in their PPAs, especially when it eats their quota. For those who do (for example, the bzr team) we're implementing multiple PPAs per person so that each PPA is able to contain different branches of code as desired (to be released in 2 months).
As Celso, says, older versions are available via direct download from Launchpad, so nobody is blocked on that. For the small benefit it would bring to be able to leave the old versions in the code compared to the effort we need to expend to implement it, I can't see it being worthwhile. I more beneficial change would be to make GDebi able to downgrade packages, then clicking .deb links in Launchpad would be a breeze.
Stuart says:
> latest and greatest bzr from the bzr PPA is not useful to them until a compatible bzrtools package is released.
This is a packaging issue, no amount of trickery on the part of PPAs will solve this. You best bet is to subscribe to the latest stable PPA rather than the development one.
The overwhelming majority of people don't need old versions floating about in their PPAs, especially when it eats their quota. For those who do (for example, the bzr team) we're implementing multiple PPAs per person so that each PPA is able to contain different branches of code as desired (to be released in 2 months).
As Celso, says, older versions are available via direct download from Launchpad, so nobody is blocked on that. For the small benefit it would bring to be able to leave the old versions in the code compared to the effort we need to expend to implement it, I can't see it being worthwhile. I more beneficial change would be to make GDebi able to downgrade packages, then clicking .deb links in Launchpad would be a breeze.
Stuart says:
> latest and greatest bzr from the bzr PPA is not useful to them until a compatible bzrtools package is released.
This is a packaging issue, no amount of trickery on the part of PPAs will solve this. You best bet is to subscribe to the latest stable PPA rather than the development one.
So sorry, this is "won't fix" for now.