So, I've managed to get a single image that supports booting both the
Pinebook and Pinebook Pro reasonably well! I can pop the microSD card
out of one and put it into the other, and it boots!
Maybe this is not a big deal to those used to x86, but in the ARM world,
it is unfortunately more complica
Hi Tanguy,
(cross-posting this to the issue itself too)
> Sorry if I'm (very) late, but apprently this hasn't made it to master
> yet, so… What the status? Do you still need a willing-but-maybe-not-qualified
> person to review or discuss your patch?
the patch set works, I can build many Python pa
Hi,
What is the standard place to put documentation?
The license files are automatically installed to the
share/doc/NAME-VERSION directory
(see install-licence-files in gnu-build-system.scm),
but it seems like various packages install the actual
documentation to share/doc/NAME.
I ask because I'm
Hi Lars,
Excerpts from Lars-Dominik Braun's message of May 17, 2021 8:24 am:
> just a quick reminder that an updated version (includes
> python-toolchain) of this proposal is still looking for a code review or
> further discussion. So if you feel confident about touching
> python-build-system, pl
Hi.,
these day I had spent some more hours struggling with rust ans cargo,
trying to get "pre-built" crates.
Summery; Cargo is cruft, no solution found yet.
I tried reusing a crate from the very same place it was built (see
enclosed script). Anyhow, this does not work since cargo uses a
dif
Am Sonntag, den 06.06.2021, 12:14 +0200 schrieb Maxime Devos:
> Leo Prikler schreef op zo 06-06-2021 om 09:39 [+0200]:
> > I think we might want to export a utility procedure
> > (patch-shebangs files inputs)
>
> This procedure already exists, but is undocumented and
> unexported. It is in (gu
Leo Prikler schreef op zo 06-06-2021 om 09:39 [+0200]:
> I think we might want to export a utility procedure
> (patch-shebangs files inputs)
This procedure already exists, but is undocumented and
unexported. It is in (guix build gnu-build-system).
(define* (patch-shebangs #:key inputs outputs
On Sat, Jun 05, 2021 at 02:09:59PM -0400, Mark H Weaver wrote:
> Hi Efraim,
>
> Efraim Flashner writes:
> > I don't really understand why
> > and how a newer kernel would make things stop working,
>
> Newer kernels _usually_ work fine, but occasionally things break, and
> that's much more likely
I think we might want to export a utility procedure
(patch-shebangs files inputs)
so that files used during build (e.g. configure, Makefile, etc.) can do
(patch-shebangs build-stuff native-inputs) and the rest implicitly gets
(patch-shebangs files inputs) during the patch-shebangs phase. WDYT?
