Date: Mon, 15 Nov 2021 16:14:15 -0500
On 12/11/2021 14.36, Ben Craig via SG15 wrote:
> I will note that there are substantial tradeoffs with absolute vs. relative paths. Both need to be an option, and the user needs to be able to use either.
>
> Absolute paths are easier to reason about and debug as an end user, and they also allow you to reference things that can't be referred to with a relative path (like items on the Windows D: driver when you are building in the Windows c: drive).
>
> Relative paths allow you to have machine independent builds, where you package all the dependencies in a well known hierarchy. This relative path approach also aids in artifact caching, as mismatched paths in command lines and built files are one way to get lots of cache misses.
...or you can use prefix-relative paths, which is what Brad was
explaining re: "relocatable packages". Those give you *both* of the above.
> I will note that there are substantial tradeoffs with absolute vs. relative paths. Both need to be an option, and the user needs to be able to use either.
>
> Absolute paths are easier to reason about and debug as an end user, and they also allow you to reference things that can't be referred to with a relative path (like items on the Windows D: driver when you are building in the Windows c: drive).
>
> Relative paths allow you to have machine independent builds, where you package all the dependencies in a well known hierarchy. This relative path approach also aids in artifact caching, as mismatched paths in command lines and built files are one way to get lots of cache misses.
...or you can use prefix-relative paths, which is what Brad was
explaining re: "relocatable packages". Those give you *both* of the above.
-- Matthew
Received on 2021-11-15 15:14:16