Marius Bakke skriver:
> Now the question is: should we restore this patch, and in practice
> restart the branch almost from scratch? Or drop it, considering
> upstream has rejected it[0]?
Following a discussion on IRC, we decided to reinstate the patch and get
rid of the newly added graft at th
Thank you! Let’s test!
On Sun, Dec 13, 2020 at 02:12:59PM -0800, John Soo wrote:
> As far as I understand it, it adds just enough to the rust package
> definition to add the extra rustfmt output.
Okay, I tweaked the commit message and pushed as
48926b588528c5a2b591e1e97a5757eb78d3cac1.
Now the branch is froz
As far as I understand it, it adds just enough to the rust package
definition to add the extra rustfmt output.
On Sun, Dec 13, 2020 at 01:50:35PM -0800, John Soo wrote:
> The patch adds an extra output, leaving the compiler unchanged so nothing
> should be effected in runtime as far as I know.
But the patch does a lot more than just add another output, right?
Hi Leo,
The patch adds an extra output, leaving the compiler unchanged so nothing
should be effected in runtime as far as I know.
- John
Hello,
icecat, ungoogled-chromium, alacritty, ripgrep, exa and others depend on it at
least. I have been using the patches for a few weeks.
What do you think?
- John
On Sun, Dec 13, 2020 at 01:44:01PM -0800, John Soo wrote:
> icecat, ungoogled-chromium, alacritty, ripgrep, exa and others depend on it
> at least. I have been using the patches for a few weeks.
>
> What do you think?
What I'm wondering is: does the patch make a simple change that is
unlikely
Leo Famulari writes:
> On Sun, Dec 13, 2020 at 12:02:50PM -0800, John Soo wrote:
>> Is there any chance this could make it to staging before the merge?
>>
>> http://issues.guix.gnu.org/42295
>
> Can you clarify what it does (I'm not that familiar with Rust).
>
> Is it likely that things will "
On Sun, Dec 13, 2020 at 12:02:50PM -0800, John Soo wrote:
> Is there any chance this could make it to staging before the merge?
>
> http://issues.guix.gnu.org/42295
Can you clarify what it does (I'm not that familiar with Rust).
Is it likely that things will "just work", or will we need to do a
Hello there,
Is there any chance this could make it to staging before the merge?
http://issues.guix.gnu.org/42295
Thanks!
John
On Sun, Dec 06, 2020 at 12:58:46PM -0500, Leo Famulari wrote:
> The plan is to start building it next Friday, December 11.
Due to reasons, there are still a few more patches to be added to the
branch. They should be pushed today.
The plan is to work on the branch this week and complete it next
we
Hello,
Newer versions of 'polkit' depend on mozjs 78, which unsurprisingly
depends on Rust.
As Rust currently only builds on x86_64, that means an important piece
of desktop systems will no longer work on other architectures.
How should we deal with this? I see a couple of options:
1. Stick wi
Am 13.12.20 um 14:21 schrieb Christopher Baines:
I think if you add openssl to --ad-hoc along with nss-certs, then you
should get the search paths setup.
Thanks, this did the trick
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@crazy-compilers.com |
| www.crazy-c
Hartmut Goebel writes:
> Hi,
>
> for setting up a guix development environment, the manual recommends
>
>guix environment guix
>
> Anyhow, this is not enough, since e.g "./preinst-env guix lint" will
> fail with "TLS certificate error". Also
>
>guix environment guix --ad-hoc nss-certs
>
Hi,
for setting up a guix development environment, the manual recommends
guix environment guix
Anyhow, this is not enough, since e.g "./preinst-env guix lint" will
fail with "TLS certificate error". Also
guix environment guix --ad-hoc nss-certs
does not succeed, since SSL_CERT_DIR sti
Hi,
how to specify "dependencies of package" in a manifest?
Background: I'm using a manifest file for defining my development
environment and keeping up with the dependencies of some of the packages
is cumbersome.
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goe...@crazy-compiler
17 matches
Mail list logo
