© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
I was more thinking of something like 'tag=OTA-6' or something, so that this can be used for other purposes than just OTA's - any image could then be tagged for various reasons. The map idea would be a good hacky solution, but I think we should design it in a complete way. And we need to make sure that all the edge cases are handled, meaning:
* Image tagged during image copy - the standard scenario for OTAs
* Image tagged after image copy
The old, existing images won't need to be handled as anyway a newer u-s-s from a newer OTA will be required for things to work. So images like OTA-4 etc. don't need to be detected (since there's no path that could lead to that being required). But still, we need to handle this rare case when someone makes a mistake and doesn't tag an image before copying it to a proper channel.