From: Efraim Flashner <efraim@flashner.co.il>
To: jgart <jgart@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: Transformations Shell Syntax
Date: Tue, 23 May 2023 11:16:57 +0300 [thread overview]
Message-ID: <ZGx2eaJJ9vaZHasi@3900XT> (raw)
In-Reply-To: <ab6cf744dbad90884658e812845349af@dismail.de>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
On Tue, May 23, 2023 at 06:43:30AM +0000, 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=8b56efa9387262514daf63151d41c9e111e79567
Obviously the difference is that --with-commit can apply to
dependencies, and this looks to only work on the actual package, but I
often find myself only adjusting the actual package I'm trying to build
anyway.
> Uses specified commit hash (short):
>
> guix build emacs-ement@8b56efa
>
> Uses latest upstream release:
>
> guix build emacs-ement@latest
>
> Uses upstream version 0.8.2 if not packaged:
>
> guix build emacs-ement@0.8.2
>
> Uses the latest commit in the wip/find-room branch:
>
> guix build emacs-ement@wip/find-room
I'm not sure how @latest would work with @wip/find-room, unless @latest
was reserved to point to (maybe) the newest release. I think we've all
seen that the updater sometimes gets confused by some of the upstream
methods of tagging releases and trying to figure out what the lastest
release actually is.
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-05-23 8:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 6:43 Transformations Shell Syntax jgart
2023-05-23 8:16 ` Efraim Flashner [this message]
2023-05-23 9:39 ` Simon Tournier
2023-05-23 13:24 ` jgart
2023-05-23 13:55 ` Andreas Enge
2023-05-23 14:12 ` jgart
2023-05-23 14:22 ` Simon Tournier
2023-05-23 14:28 ` Andreas Enge
2023-05-23 17:20 ` jgart
2023-05-24 3:06 ` Ryan Prior
2023-05-26 15:50 ` Ludovic Courtès
2023-05-27 17:07 ` John Kehayias
2023-07-02 19:54 ` Ludovic Courtès
2023-07-05 20:23 ` John Kehayias
2023-07-03 0:01 ` jgart
2023-07-16 13:14 ` Ludovic Courtès
2023-07-23 13:00 ` Hartmut Goebel
2023-08-16 14:03 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZGx2eaJJ9vaZHasi@3900XT \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=jgart@dismail.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.