> What's the shepherd-for-guix patch ? What does it bring to Shepherd ?
https://issues.guix.gnu.org/54216
it basically introduces a shepherd-next package. it's one way to
greatly shorten the edit-compile-test cycle of shepherd within a guix
system vm.
in the current setup, changing the shepherd
Hello, gentle maintainer.
This is a message from the Translation Project robot. (If you have
any questions, send them to .)
A new POT file for textual domain 'shepherd' has been made available
to the language teams for translation. It is archived as:
https://translationproject.org/POT-file
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'shepherd' has been submitted
by the Ukrainian team of translators. The file is available at:
https://translationproject.org/latest/shepherd/uk.po
(We can arrange things so
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'shepherd' has been submitted
by the German team of translators. The file is available at:
https://translationproject.org/latest/shepherd/de.po
(We can arrange things so tha
Liliana Marie Prikler schreef op do 31-03-2022 om 06:22 [+0200]:
> > It should be possible to look for ‘# Generated by GNU Autoconf’ and
> > ‘# Makefile.in generated by automake’ lines in some 'find-
> > generated-autotools-fies’or something.
> I don't think that will work correctly. Case in point
Zhu Zihao schreef op wo 30-03-2022 om 22:31 [+0800]:
> It is also burden for
> packager to pick the build-time dependencies like libtool,
> autoconf-archive, gnulib etc. if we force all autotools baseed
> packages use autoreconf
Reading 12037 lines of 'configure' and 7896 lines of 'Makefile.in'
se
Zhu Zihao schreef op wo 30-03-2022 om 22:31 [+0800]:
> For software developer, they prefer to bundle a generated configure
> script because it will be a bootstrap problem sometimes.
Sometimes that's convenient for upstream, but how is this relevant to
downstream (Guix)? Downstream does not have t
Zhu Zihao schreef op wo 30-03-2022 om 22:31 [+0800]:
> A simple examples,the m4 macro GUILE_PKG defined in guile.m4 helps
> autotools to check guile installation. If there's no generated
> configure
> script. Software user should have guile.m4 to generate configure
> script.
> A macro that detects
Zhu Zihao schreef op wo 30-03-2022 om 22:31 [+0800]:
> Because you can't track all files that generated by Autotools.
You can. Just look for files named 'configure', 'Makefile.in',
'Makefile.in.in', and to reduce false positives, look inside the files
for the "Generated by ..." string.
Also look
Hi guix,
Often, when new rust package definitions are submitted at guix-
patches@, I see #:skip-build? #false. Apparently it's added by default
in (guix import cargo), with some exceptions. However, ‘(guix)Rust
Crates’ states:
Care should be taken to ensure the correct version of dependencie
Hi!
I did a similar experiment as you did, but using the GCC tarball (I was
too lazy to wait for ungoogled-chromium’s tarball), like so:
--8<---cut here---start->8---
$ xz -d < /gnu/store/x043r7crzd0p0p5cfky8r6hwsxknhkk0-gcc-11.2.0.tar.xz | zstd
-19 > /tmp/gcc
Am Donnerstag, dem 31.03.2022 um 13:10 +0200 schrieb Maxime Devos:
> Liliana Marie Prikler schreef op do 31-03-2022 om 06:22 [+0200]:
> > > It should be possible to look for ‘# Generated by GNU Autoconf’
> > > and
> > > ‘# Makefile.in generated by automake’ lines in some 'find-
> > > generated-auto
Liliana Marie Prikler schreef op do 31-03-2022 om 20:24 [+0200]:
> > What would not work correctly here?
> grep "[Gg]enerated" pre-inst-env
I suggest:
1. check that the file name is "configure" or "Makefile.in"
2. and search for "[Gg]enerated by (automake|GNU Autoconf)"
3. If (1) and (2) ma
Hi Maxime,
similar discussions have been had in the past, but thanks for raising
them again. As far as I'm aware, the "consensus" – if it can be called
such – is that due to Rust packages often being a giant nothing burger
both in terms of what they actually do and in what can be used for
subsequ
Liliana Marie Prikler schreef op do 31-03-2022 om 21:07 [+0200]:
> Hi Maxime,
>
> similar discussions have been had in the past, but thanks for raising
> them again. As far as I'm aware, the "consensus" – if it can be called
> such – is that due to Rust packages often being a giant nothing burger
Hi,
since rust does not support anything like static or dynamic libraries,
building (intermediate) crates is useless like a hole in my head. Any
output on any intermediate crate will just be thrown away.
Often, when new rust package definitions are submitted at guix-
patches@, I see #:skip-b
Hartmut Goebel schreef op do 31-03-2022 om 21:47 [+0200]:
since rust does not support anything like static or dynamic libraries,
building (intermediate) crates is useless like a hole in my head. Any
output on any intermediate crate will just be thrown away.
In my experiments, it looks like the r
Am Donnerstag, dem 31.03.2022 um 20:31 +0200 schrieb Maxime Devos:
> Liliana Marie Prikler schreef op do 31-03-2022 om 20:24 [+0200]:
> > > What would not work correctly here?
> > grep "[Gg]enerated" pre-inst-env
>
> I suggest:
>
> 1. check that the file name is "configure" or "Makefile.in"
>
On 2022-01-03 16:22, Ludovic Courtès wrote:
I suppose people could explicitly Cc: the team you’re on when they need
specific advice or review; that should already help.
Having some topic-specific streams I could tap into would allow me to
be
a little more proactive.
This brings a related bu
Hello,
From time to time, I think about audio/video mixer (.i.e. video conference
software like BBB or Jitsi) , with the intension of making it highly modular
that it can be freely remixed and reinvented by volunteer participants.
Is anyone interested? Or is can you think about something that
Dear reviewer,
in the sequel find the new review checklist, effective immediately.
Failure to apply it will result in the confiscation of your machine for
the purpose of making it usable for continuous integration.
Happy April Fools
-
So you want to package a
[ ] C [ ] C++ [ ] C# [ ]
Liliana Marie Prikler schreef op vr 01-04-2022 om 06:14 [+0200]:
> It won't be added to Guix. Here's why it won't.
> You appear to believe that
> [...]
> [ ] hard-coding the commit field is a good idea
Does the following count:
(define-public foo
(package
(name "foo")
(version "1.0.0")
Dear Liliana,
On 2022-04-01 04:14, Liliana Marie Prikler wrote:
in the sequel find the new review checklist, effective immediately.
Failure to apply it will result in the confiscation of your machine for
the purpose of making it usable for continuous integration.
The last patch I submitted se
23 matches
Mail list logo
