[ Keeping you in CC; you are likely not subscribed to this "old" Alioth list but let me know if you are and I will drop the explicit copy in future ]
Hi Stéphane, > But to what value should the build path prefix be set to? Two > possibilities comes to my mind: either some absolute path like > /usr/src/$srcpkg or just ".". Until we see more adoption I would not label it as a "best practice" just yet but the pattern so far has been to set it to ".". For example, this is exactly what Debian does when adding -ffile-prefix- map to CFLAGS via dpkg-buildflags(1): https://git.dpkg.org/cgit/dpkg/dpkg.git/tree/scripts/Dpkg/Vendor/Debian.pm#n246 > Is there a way that the toolchain automatically sets > BUILD_PATH_PREFIX_MAP? I would share your reservations about scalability and would append my own æsthetic problems with ugly boilerplating. However, I notice that a "dh-ocaml" package exists and although this might be for a more narrower use-case (alas I am not an OCaml developer) this might be both the cleanest solution and moreover the most pragmatic one; exporting to the environment via debhelper more generally á la SOURCE_DATE_EPOCH or even by dpkg itself would likely be more of a difficult ask. Regards, -- ,''`. : :' : Chris Lamb `. `'` [email protected] 🍥 chris-lamb.co.uk `- _______________________________________________ Reproducible-builds mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/reproducible-builds
