Code review comment for lp:~thomas-voss/mir/explicit-gcc-version
Revision history for this message
| Alan Griffiths (alan-griffiths) wrote | # |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
I'm still trying to understand what I'm missing and how this gains anything.
Without this change we'll experience "issues" as soon as any of our upstream, downstream or mir projects are built with an ABI incompatible compiler version. We then need to ensure that all relevant projects get rebuilt.
With this change we'll experience "issues" as soon as any of our upstream, downstream or mir projects are built with an ABI incompatible compiler version. We then need to ensure that all relevant projects get rebuilt.
The differences are:
1. In the first case the trigger is a new compiler in archive, in the second the trigger is some project updating an explicit dependency.
2. In the second case the explicit dependencies for all the relevant projects need to be updated in addition to forcing the rebuilds.