Danny Milosavljevic <dan...@scratchpost.org> writes: > Hi, > >>+ (copy-file (assoc-ref inputs "fpc-binary") >>+ "fpc-bin.tar") >>+ (zero? (system* "tar" "xvf" "fpc-bin.tar"))))) > > Why the copy-file and then untar ? Can't it be untarred immediately from > where it is? If it is useful, maybe add a comment about the reason. > > Also, it might be easier to have a fpc-bootstrap package with the bootstrap > binaries that installs the binaries required to build fpc normally and to > make a fpc package depend on fpc-bootstrap as native-inputs. What do you > think? I myself don't have a strong preference about it - but some other > packages do it that way.
It’s not so nice to depend on a binary bootstrap. Can this be avoided? I tried packaging a version of the GNU Pascal compiler, which is unmaintained, in an effort to bootstrap a version of FPC from source. Have you attempted this? -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net
