SBP via <[email protected]> writes: > Hi! > > I just started using Guix as a package manager, and I'm having a problem where > the substitute of a package (let's call it A) has a bad file (missing value > in a > #define) that prevents compilation of another package (let's call it B) which > depends on it.
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. > > My question is, is it somehow possible to inform the package > definition of B (or guix in general) to not use a substitute for A, > but rather compile A from source? > > I searched the manual but couldn't find a reference to this. 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. Tomas -- There are only two hard things in Computer Science: cache invalidation, naming things and off-by-one errors.
signature.asc
Description: PGP signature
