Hi Liliana,
(Efraim, I've Cc'd you since you're working on re-doing Rust inputs.)
Liliana Marie Prikler writes:
> Does anyone have an idea how we should handle propagations for the sake
> of pkg-config? Perhaps we could add "linked-inputs", which are added
> when building packages and
Yo all!
Just put the latest nightly Mobian again on my pinephone--I am going to
attempt to put Guix on it over the next couple days.
I will keep everyone posted on how the process goes (:
~vidak
On 2021-09-02 15:59, Christine Lemmer-Webber wrote:
> Joshua Branson writes:
>
>> Hey Guix!
>>
> From section 3.3.1 in the manual:
> https://www.gnu.org/software/mes/manual/mes.html
>
> "Setting MES to a mes-compatible Scheme will run mescc using that"
>
> What is a "mes-compatible Scheme"? That term does not appear again in the
> page.
I'm not sure but I'd say that applies to Mes and
For some clarity on the situation:
http://www.fsfla.org/pipermail/linux-libre/2021-August/003439.html
The scripts are not being removed and my understanding is that Guix
only uses the scripts anyway.
> and their Git repo is also going to be rewritten to remove them.
The tags for the kernel
On Fri, Sep 03, 2021 at 10:03:47PM +0200, Xinglu Chen wrote:
> ‘guix describe’ would show the commit of the guix.git repo used,
> wouldn’t it?
It shows the commit of currently effective revision of Guix, but it can't
tell you what revision of Guix a built package came from.
> If the date is not
From section 3.3.1 in the manual:
https://www.gnu.org/software/mes/manual/mes.html
"Setting MES to a mes-compatible Scheme will run mescc using that"
What is a "mes-compatible Scheme"? That term does not appear again in the page.
Hi Guix,
some while ago we made the decision to propagate inputs, that are
mentioned in pkg-config files, the rationale being that those
propagated inputs will be needed in packages in order to compile. This
has saved us some typing, but at a cost. For instance, it is now no
longer possible to
According to the linux-libre team in the #gnu-linux-libre IRC channel on
Libera.chat, all releases of linux-libre before 4.4.282, 4.9.281,
4.14.245, 4.19.205, 5.4.143, 5.10.61, and 5.13.13 will be deleted from
their servers, and their Git repo is also going to be rewritten to
remove them.
So, if
Hi list,
I hope this topic gets attention. As far as I can tell, this is a blocker
against 45692 getting merged.
I am already annoyed enough with 45692 (it has been about half a year or so
since submitted) and will not prioritize updating the patch until I can expect
the CDDL-GPL
On 04.09.2021 00:11, Liliana Marie Prikler wrote:
>
> Well, let #f or *unspecified* would also solve the git blame issue, [...]
>
Only partially on-topic but: I believe *unspecified* should not be used
explicitly in code. It's an implementation detail, and by avoiding it in
user code, we lessen
10 matches
Mail list logo
