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
Looks like Hoard's Makefile and GNUmakefile clone master of Heap-Layers. Unless you never change Heap-Layers, it seems likely that at some point you will introduce a change to Heap-Layers that will require a corresponding change to Hoard. When that happens, old versions of Hoard (which might be present in package management systems) will no longer be able to build. This problem might not always be noticed right away, leaving your software in broken state in that package management system for an unbounded period of time.
For this reason, you should download a specific version of Heap-Layers that is known to work with this version of Hoard.
I think git already behaved that way before when you were using submodules, so you could get this behavior back by reverting 5275686 and also making the same change to GNUmakefile.
The text was updated successfully, but these errors were encountered:
Looks like Hoard's Makefile and GNUmakefile clone master of Heap-Layers. Unless you never change Heap-Layers, it seems likely that at some point you will introduce a change to Heap-Layers that will require a corresponding change to Hoard. When that happens, old versions of Hoard (which might be present in package management systems) will no longer be able to build. This problem might not always be noticed right away, leaving your software in broken state in that package management system for an unbounded period of time.
For this reason, you should download a specific version of Heap-Layers that is known to work with this version of Hoard.
I think git already behaved that way before when you were using submodules, so you could get this behavior back by reverting 5275686 and also making the same change to GNUmakefile.
The text was updated successfully, but these errors were encountered: