I don't like the unpredictability of jgart's original proposal, but maybe
something explicit could still look similar.
Suppose you could build emacs-ement these three ways:
# no transform- this is a version packaged in Guix
guix build emacs-ement@0.5.2
# transform using `with-git-commit`
guix bui
Hi Florian!
> in German I have translated in this way and it got
> accepted.
Yes, my fellow Swedish translator pointed that out to me! :)
I will contribute a similar translation in Swedish, but I also
want the bug in the original code fixed.
I have attached my attempt at a patch to this mail.
Ma
> What disturbs me with your suggestion is that it reuses the same syntax
> that is already used for a different purpose. So in a sense you do
> "operator overloading", and the same command line then means different
> things depending on whether the package version is already provided by
> Guix or
Hi Timothy,
On Tue, May 23, 2023 at 12:31 AM Timothy Washington wrote:
>
> Yes that was it! I added "(native-inputs (list perl python))" to my package
> definition.
>
> $ guix build -L ~/dotfiles/ rust-rustscan # A. Now builds again!
Hats off to Tobias Kortkamp for pinpointing the issue so co
Hi Tim,
--- Original Message ---
On Monday, May 22nd, 2023 at 8:20 PM, Timothy Washington
wrote:
> Yes that was it! I added "(native-inputs (list perl python))" to my package
> definition.
> $ guix build -L ~/dotfiles/ rust-rustscan # A. Now builds again!
> /gnu/store/4bldy27x1f2mzjqg
Am Tue, May 23, 2023 at 02:12:02PM + schrieb jgart:
> > I think your semantics ends up meaning "try to make sense of the version
> > field, and give me the package at this version".
> Aren't these the current semantics of guix package transformations though?
> I'm just proposing shell syntax
Hi jgart,
On Tue, 23 May 2023 at 16:12, jgart wrote:
> Aren't these the current semantics of guix package transformations though?
> I'm just proposing shell syntax for them.
The main difference is explicit vs implicit. The current syntax is
explicit. The one you are proposing is implicit. A
> I am a bit wary of too much intelligence in interpreting commands, at the
> expense of clarity
Hi Andreas,
I agree with this design aesthetic.
Personally, I like my software not too dumb and not too smart with a slight
bias towards the smart.
> I think your semantics ends up meaning "try to
Hello,
Am Tue, May 23, 2023 at 01:24:00PM + schrieb jgart:
> I was openly ideating on having shell syntax like we do currently for
> emacs-ement@0.9.3, for example, but for a subset of package transformation
> options as well.
I am a bit wary of too much intelligence in interpreting command
> WDYT about what? Could you be more specific and detail your idea?
Hi Simon,
I was openly ideating on having shell syntax like we do currently for
emacs-ement@0.9.3, for example, but for a subset of package transformation
options as well.
Does that clarify my intent?
If not, let me know to
Hi jgart,
On Tue, 23 May 2023 at 06:43, "jgart" wrote:
> Hi Guixers WDYT,
WDYT about what? Could you be more specific and detail your idea?
> Uses specified commit hash:
>
> guix build emacs-ement@8b56efa9387262514daf63151d41c9e111e79567
>
> Uses specified commit hash (short):
>
> guix build
Hi Sebastian, in German I have translated in this way and it got
accepted. Although, I have not actually tested if it displays
correctly. I assume Guile formatting is tolerant.
#: modules/shepherd/service.scm:1087
#, scheme-format
msgid "Cannot unregister service ~a, which is still running"
msgi
Hi!
I think it's indeed a bug in the Shepherd. Both forms should be identical for
singular and plural. Especially, I think we should use ~{ ~a,~} in both cases
since even when there's a single service, the argument is a list, so with only
~a, it wouldn't show properly.
Le 23 mai 2023 01:57:05
On Tue, May 23, 2023 at 06:43:30AM +, jgart wrote:
> Hi Guixers WDYT,
>
> Uses specified commit hash:
>
> guix build emacs-ement@8b56efa9387262514daf63151d41c9e111e79567
for a comparison, the current (long) version:
guix build emacs-ement
--with-commit=emacs-ement=8b56efa9387262514daf63151
Hi Csepp,
2023/05/20 00:29, Csepp:
> Remco van 't Veer writes:
>
>> Hi Maxim and Zimoun,
>>
>> 2023/02/09 13:26, Remco van 't Veer:
>>
>>> I think I know what is causing the issue. Both the "standard" mysql and
>>> postgres containers use user-id 999 to run the database service (this
>>> seems
* gnu/services/docker.scm (docker-configuration): Define the argument.
* gnu/services/docker.scm (docker-shepherd-service): Use it.
* doc/guix.texi (Docker Service): Document it.
---
doc/guix.texi | 27 ++-
gnu/services/docker.scm | 28 +++-
Yes that was it! I added "(native-inputs (list perl python))" to my package
definition.
$ guix build -L ~/dotfiles/ rust-rustscan # A. Now builds again!
/gnu/store/4bldy27x1f2mzjqg5jd176nrawl98y1y-rust-rustscan-2.1.1
$ guix package -L ~/dotfiles/ -m ~/dotfiles/guix/packages/manifest.scm #
B.
This was also touched on in the email thread "*Howto reference a custom
package from a manifest*". But I also wanted to acknowledge that "*Solution:
add perl to native-inputs*" was indeed the right answer. So thanks for
that.
I added "(native-inputs (list perl python))" to my package definition.
Hi!
I'm involved in the translation of Shepherd to Swedish, and
poedit complains that the format specifications for the singular
and plural forms of one of the strings are not the same:
https://git.savannah.gnu.org/cgit/shepherd.git/tree/modules/shepherd/service.scm#n1107
Later on in the source t
19 matches
Mail list logo
