Hi,
I'm wondering what the overall estimated work or effort might look like to
leverage Guix to build a co-existing family of packages that are in some sense
"orthogonal" to the rest of Guix, based upon different package versions and
perhaps musl libc - similar to
Hi guix-devel!
On Sun, Feb 12, 2023 at 03:49 PM, Josselin Poiret wrote:
> Hi everyone,
>
> Andreas Enge writes:
>
>> I volunteer to follow your lead, but also have no clue what is actually
>> expected.
>
> I would also like to give a hand!
>
Count me in as well!
I only did some spot fixes the
Hello Josselin,
Am Sun, Feb 12, 2023 at 10:13:35PM +0100 schrieb Josselin Poiret:
> For a potential roadmap (doesn't have to be sequential):
> 1. Document this workflow in the manual, in a dedicated node, with a
>rationale as well. One thing worth mentioning would be how to handle
>
Hi Andreas and thanks for taking the notes during the discussion!
I think what came out of that discussion was very interesting and that
it would greatly help the scaling problems Guix is facing as well as
maintainer/contributor burnout, but that also means that we need to
create some actionnable
On Thu, Dec 15, 2022 at 03:56:24PM +0100, Ludovic Courtès wrote:
> Hi,
Sorry for taking a while to get back to answer this.
> Efraim Flashner skribis:
>
> > On December 12, 2022 1:47:29 PM UTC, "Ludovic Courtès" wrote:
>
> [...]
>
> >>> + ,@(if (target-arm?)
> >>> + ;; Some
Andreas Enge writes:
> Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller:
>> And I was able to rebuild (with --check) patch-mesboot. The error looks
>> a lot like https://issues.guix.gnu.org/49985. We should fix that indeed
>> :)
>
> Ah indeed, that looks like deal breaking; maybe
Hi,
--- Original Message ---
On Sunday, February 12th, 2023 at 5:08 PM, Andreas Enge wrote:
>
>
> Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller:
>
> > And I was able to rebuild (with --check) patch-mesboot. The error looks
> > a lot like
Csepp writes:
> I thought I agreed when I sent my part, but in case I haven't:
> I agree to licensing your contribution under CC-BY-SA 4.0 and GFDL
> version 1.3 or later, with no Invariant Sections, no Front-Cover Texts,
> and no Back-Cover Texts.
s/your/mine/
I copied the text from the
Am Sun, Feb 12, 2023 at 12:58:06PM +0100 schrieb Julien Lepiller:
> And I was able to rebuild (with --check) patch-mesboot. The error looks
> a lot like https://issues.guix.gnu.org/49985. We should fix that indeed
> :)
Ah indeed, that looks like deal breaking; maybe someone from MES can have
a
On Sun, Feb 12, 2023 at 10:05:40AM +0100, Julien Lepiller wrote:
> Hi Guix!
>
> As discussed at Guix Days before Fosdem, we haven't merged core-updates
> in a very long time. I'd volunteer to lead this effort, but I don't
> know what steps I should follow. Do we have some documentation about
>
Hi!
Not a review, but how is *tif ‘not an X toolkit’...? Why not just say it ‘uses
*tif’, instead?
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
Hi everyone,
Andreas Enge writes:
> I volunteer to follow your lead, but also have no clue what is actually
> expected.
I would also like to give a hand!
> [...]
> Actually I am wondering whether the first step of killing these untamed
> non-feature branches would not be to build and merge
Julien Lepiller writes:
> As discussed at Guix Days before Fosdem, we haven't merged core-updates
> in a very long time. I'd volunteer to lead this effort, but I don't
> know what steps I should follow. Do we have some documentation about
> that?
I can try and help with this, at least in terms
Julien Lepiller writes:
> Le Sun, 12 Feb 2023 12:52:51 +0100,
> Julien Lepiller a écrit :
>
>> Le Sun, 12 Feb 2023 12:06:14 +0100,
>> Andreas Enge a écrit :
>>
>> I just tried to build mpc on my machine, from core-updates. I get the
>> same derivation as the one shown on the data service,
On Sun, Feb 12, 2023 at 10:05:40AM +0100, Julien Lepiller wrote:
> As discussed at Guix Days before Fosdem, we haven't merged core-updates
> in a very long time. I'd volunteer to lead this effort, but I don't
> know what steps I should follow. Do we have some documentation about
> that?
The
Le Sun, 12 Feb 2023 12:52:51 +0100,
Julien Lepiller a écrit :
> Le Sun, 12 Feb 2023 12:06:14 +0100,
> Andreas Enge a écrit :
>
> I just tried to build mpc on my machine, from core-updates. I get the
> same derivation as the one shown on the data service, and it built
> fine. Maybe there's
Le Sun, 12 Feb 2023 12:06:14 +0100,
Andreas Enge a écrit :
> Hello,
>
> Am Sun, Feb 12, 2023 at 10:05:40AM +0100 schrieb Julien Lepiller:
> > As discussed at Guix Days before Fosdem, we haven't merged
> > core-updates in a very long time. I'd volunteer to lead this
> > effort, but I don't know
Hello,
Am Sun, Feb 12, 2023 at 10:05:40AM +0100 schrieb Julien Lepiller:
> As discussed at Guix Days before Fosdem, we haven't merged core-updates
> in a very long time. I'd volunteer to lead this effort, but I don't
> know what steps I should follow. Do we have some documentation about
> that?
Ludovic Courtès writes:
Hello!
Thanks Simon for pinging me!
> You might remember that I started long ago asking people who had
> contributed to the blog whether they would agree to licensing their work
> under CC-BY-SA 4.0 and GFDL version 1.3 or later, with no Invariant
> Sections, no
Hi Guix!
As discussed at Guix Days before Fosdem, we haven't merged core-updates
in a very long time. I'd volunteer to lead this effort, but I don't
know what steps I should follow. Do we have some documentation about
that?
20 matches
Mail list logo
