Am Sonntag, dem 13.02.2022 um 16:51 -0500 schrieb Philip McGrath: > This might seem a bit silly in isolation, but it makes the structure > of the upstream Chez Scheme package the same as for the Racket > variant, it sets things up for (one day, hopefully) actually being > able to bootstrap the upstream Chez Scheme bootfiles, and it may be > useful for cross-compilation and adding support for architectures > without pre-built bootfiles from upstream. > > * gnu/packages/chez-and-racket-bootstrap.scm > (chez-scheme-bootstrap-bootfiles): New variable. > (chez-scheme)[native-inputs]: Add it. > [arguments]: Add new phase 'unpack-bootfiles'. > [version, source, home-page]: Derive from 'chez-scheme-bootstrap- > bootfiles'. > --- While having chez-scheme-bootstrap-bootfiles (silly name) does make some kind of sense, making chez-scheme inherit from it does not. Given that we don't have a chez-scheme bootstrap tower at hand, you should probably make (chez-scheme-bootstrap) a procedure which takes chez- scheme's origin as argument and returns the full package. Also, while technically a violation of the DRY principle, you are allowed to type out the homepage multiple times.