archives as dependencies #5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
local libraries being rebuilt is currently ignored by the dependency chain, meaning that top nodes won't be marked as outdated and will not be rebuilt on their own
would appending
${ARCHIVES}to the${NAME}recipe suffice ?we do not need to rebuild node level objects when archive objects changed right ?
what about archive headers
if we're basing ourselves on the date of archives themselves then any change would mark nodes as outdated
i would argue that just to be safe we should rebuild upon noticing any change to any library, unless we took the trouble to dissect this further which is probably not worth the effort and may not even be able to be realised in a fool proof manner