Hi! (I’m late to the party…)
Pjotr Prins <pjotr.publi...@thebird.nl> skribis: > As Guix takes care of the first and the last - the issue centers > around building. The idea is to dress down these language specific > builders, such as cargo, so you don't have all the included > complexity. > > A sexp-pack would represent the most simple build instructions to > build a package on its own. Now, of course the current guix-builders > solve that too. But, what I am proposing is to split out the actual > build step into a package definition, so as to present something > simpler to Guix. > > I found a cargo -> ninja converter. It is that kind of idea. Guix > would use ninja with rustc instead of cargo. A stripped down cargo > could potentially work too - but cargo is a complex beast. In a way, aren’t importers addressing this use case? In the end, they let everyone develop a package manager/build system that suits their needs, while still allowing us to have our cake. WDYT? Ludo’.
