Bug#1004939: debhelper: Drop -DCMAKE_SKIP_RPATH=on in compat v14

2022-03-14 Thread Vagrant Cascadian
On 2022-03-05, Vagrant Cascadian wrote: > On 2022-02-16, Andrea Pappacoda wrote: >> But if what you are trying to solve is a reproducibility issue then >> CMAKE_BUILD_RPATH_USE_ORIGIN should be enough, and shouldn't even >> break existing workflows. > > That's been my experience so far, I've

Bug#1004939: debhelper: Drop -DCMAKE_SKIP_RPATH=on in compat v14

2022-03-05 Thread Vagrant Cascadian
On 2022-02-16, Andrea Pappacoda wrote: > Hi, I think that CMAKE_SKIP_RPATH a bit extreme too. Also, setting both > options doesn't make much sense, as CMAKE_SKIP_RPATH completely avoids > setting the rpath, so CMAKE_BUILD_RPATH_USE_ORIGIN does nothing :/ Well, it makes it "easy" to fallback to

Bug#1004939: debhelper: Drop -DCMAKE_SKIP_RPATH=on in compat v14

2022-02-03 Thread Vagrant Cascadian
Package: debhelper Version: 13.6 Severity: normal User: reproducible-bui...@lists.alioth.debian.org Usertags: buildpath toolchain X-Debbugs-Cc: Vagrant Cascadian , reproducible-b...@lists.alioth.debian.org The debhelper compat level v14 is still experimental, and I think it might be worth