Hi Tomas >I feel like this opens so many questions. How did that happen? >Substitute should be just a built package, so it should not matter, >content-wise, whether you build the package locally or substitute it.
In general, yes. But when a package generates sources at compile-time based on configure flags, there can be discrepancies between the substitute and the local build (with different flags). >If you control the package A, you can put #:substitutable? #f into its >arguments. If A is an upstream package, you should bug-report this, >because what you are describing should *not* happen. Thanks, that parameter had escaped my attention. Yes, I've reported this upstream (see [1], in case you're interested). Cheers! [1] https://codeberg.org/guix-science/guix-science/issues/859
