You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2020. It is now read-only.
Current implementation of install phony target mimics how legacy system handles this: just make more phony targets and install things repetitively, i.e. no dependency tracking. So we always copy stuff to the destination, no matter whether this might a waste.
Also, as in #342, we can leverage on Shake's builtin dependency tracking to install packages in the right order, instead of hardcoding the order or reinventing a topSort ourselves.
The text was updated successfully, but these errors were encountered:
Current implementation of
install
phony target mimics how legacy system handles this: just make more phony targets and install things repetitively, i.e. no dependency tracking. So we always copy stuff to the destination, no matter whether this might a waste.Also, as in #342, we can leverage on Shake's builtin dependency tracking to install packages in the right order, instead of hardcoding the order or reinventing a
topSort
ourselves.The text was updated successfully, but these errors were encountered: