l...@gnu.org (Ludovic Courtès) skribis: > What about: > > 1. Computing the list of search-path-specifications of all the > transitive inputs of the package, the way ‘package-derivation’ > does it; > > 2. Computing, based on these specifications and all the input > derivations, the actual search paths, the way ‘set-paths’ does it?
As discussed on IRC, that won’t work because ‘build-system’ implementations augment the search path specifications on their own, and there’s no good way from the outside to tell what these are. Bummer. Ludo’.
