Bringing some dependencies in house

[oleg-alexandrov]

Back when Isaac started we looked around at the best packages to use for some of the work that we then built on. That was a good thing, but longer term having the isaac repo depend on third-party repos that may go away without notice is likely a fragile state of things.

When there's more dev time, perhaps one can look at this list of third-party deps, https://github.com/oleg-alexandrov/mvs-texturing/blob/isaac/elibs/CMakeLists.txt, and switch those to some forked repos under nasa/isaac. Even my own repo, as seen above, should be forked I think.

This came about because I managed to break some stuff in those dependencies (that I fixed with Marina). That was made robust now, by ensure a specific version is checked out, but the longer term dependency on repos whose history may be rewritten or even they may be deleted is still there.

[marinagmoreira]

@bcoltin what are your thoughts on this? Even now we're adding more and more forked repos in our accounts, I have a couple as well as Brian K. But I don't think we can have forks under nasa/isaac and an organizations can't fork repos under the free account (and that would be a big hassle)

[bcoltin]

I think this is a good idea but the effort / reward ratio is very poor. I think if we do want to make this more robust, our effort would be better spent getting the minor patches we need merged upstream if possible...

[trey0]

A simple though imperfect way to make this more robust would be: for every place we depend on a repo personal fork, make sure there is a redundant personal fork containing the same required frozen commit, and keep some notes about where those redundant forks are in case we need to swap out a broken link.