Is it acceptable practice to have package dependencies built in
deps/ with hardcoded absolute paths? I don’t see a reason why not, since I’d assume that in general it is hard to avoid this with external dependencies and I also do not see a use case where I build a package and then move it do a different location. However, I was wondering if I am missing something…
Note that the original poster on Slack cannot see your response here on Discourse. Consider transcribing the appropriate answer back to Slack, or pinging the poster here on Discourse so they can follow this thread.
(Original message ) (More Info)