scripts: revert changes that led to accumulation of old packages #1474
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HiassofT
approved these changes
Mar 23, 2017
lrusak
approved these changes
Mar 24, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a package version is bumped this change allowed the old package to remain in the build directory.
Although undesirable (and unintended), normally this wouldn't be a huge problem unless performing a wildcard copy as in the case of bcm2835-bootloader/release.
Reverting this change restores the original behaviour which is correct (now that I fully understand why it's doing what it is/was doing!)
Thanks and apologies to @HiassofT and indri :)
(No need for a backport, these changes are LE9 only)