[PATCH] doc: Note that guix package can operate on outputs.

DoneSubmitted by Abhishek Cherath.
Details
3 participants
  • Abhishek Cherath
  • Tobias Geerinckx-Rice
  • zimoun
Owner
unassigned
Severity
normal
A
A
Abhishek Cherath wrote on 23 Nov 19:37 +0100
(address . guix-patches@gnu.org)(name . Abhishek Cherath)(address . abhi@quic.us)
20221123183733.3889-1-abhi@quic.us
* doc/guix.texi ("Package Management")
["Invoking guix package"]: Mention support for operating
on store paths.
---
doc/guix.texi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)

Toggle diff (21 lines)
diff --git a/doc/guix.texi b/doc/guix.texi
index c0cb24d709..70c473bdf6 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -3424,9 +3424,10 @@ The @var{options} can be among the following:
 Install the specified @var{package}s.
 
 Each @var{package} may specify either a simple package name, such as
-@code{guile}, or a package name followed by an at-sign and version number,
+@code{guile}; a package name followed by an at-sign and version number,
 such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
-case, the newest version prefixed by @code{1.8} is selected).
+case, the newest version prefixed by @code{1.8} is selected); or a store path,
+such as @file{/gnu/store/qyrids57rb050vdzsdskdf7p59nlchnv-guile-1.8.8}.
 
 If no version number is specified, the
 newest available version will be selected.  In addition, @var{package}

base-commit: 7a2082023ad9c7479bfedf39537606a088222d48
-- 
2.38.1
A
A
Abhishek Cherath wrote on 23 Nov 19:47 +0100
(address . 59520@debbugs.gnu.org)(name . Abhishek Cherath)(address . abhi@quic.us)
20221123184750.4305-1-abhi@quic.us
* doc/guix.texi ("Package Management")
["Invoking guix package"]: Mention support for operating
on store paths.
---
doc/guix.texi | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)

Toggle diff (21 lines)
diff --git a/doc/guix.texi b/doc/guix.texi
index c0cb24d709..61f323446b 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -3424,9 +3424,10 @@ The @var{options} can be among the following:
 Install the specified @var{package}s.
 
 Each @var{package} may specify either a simple package name, such as
-@code{guile}, or a package name followed by an at-sign and version number,
+@code{guile}; a package name followed by an at-sign and version number,
 such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
-case, the newest version prefixed by @code{1.8} is selected).
+case, the newest version prefixed by @code{1.8} is selected); or a store path,
+such as @file{/gnu/store/...-guile-1.8.8}.
 
 If no version number is specified, the
 newest available version will be selected.  In addition, @var{package}

base-commit: 7a2082023ad9c7479bfedf39537606a088222d48
-- 
2.38.1
Z
Z
zimoun wrote on 23 Nov 21:35 +0100
(name . Abhishek Cherath)(address . abhi@quic.us)
86o7sxflz8.fsf@gmail.com
Hi,

On Wed, 23 Nov 2022 at 13:47, Abhishek Cherath <abhi@quic.us> wrote:

Toggle quote (2 lines)
> -@code{guile}, or a package name followed by an at-sign and version number,
> +@code{guile}; a package name followed by an at-sign and version number,
-^
Why this change comma -> semicolon ?

Toggle quote (4 lines)
> such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
> -case, the newest version prefixed by @code{1.8} is selected).
> +case, the newest version prefixed by @code{1.8} is selected); or a store path,
> +such as @file{/gnu/store/...-guile-1.8.8}.
-^

Idem here.

BTW, I am not convinced that people would install a package by referring
by its store path. I mean, it is impossible to know beforehand the
hash.

What is your use case?

Cheers,
simon
A
A
Abhishek Cherath wrote on 23 Nov 22:02 +0100
55329d6b-623f-c791-07c2-4eb219ca67d2@quic.us
Hello,

That change was to make the hierarchy of clauses a bit clearer (A such
as a, or b; B such as a, or b; or C such as a, or b), that being said
it is just a style thing, I can change it back if preferred.

Well I had to do it today! (rust 1.65 is defined but not exported, so to
install it I ran `guix build -e '(@@ (gnu packages rust rust-1.65)'`,
then `guix install /gnu/store/...-rust-1.6.5`

I do agree that it's maybe not the best to have it in the same sentence
though, but it'd be nice to have this behavior documented.

Thanks,
Abhishek.

(Sorry forgot to reply all on previous email)

On 11/23/22 15:35, zimoun wrote:
Toggle quote (25 lines)
> Hi,
>
> On Wed, 23 Nov 2022 at 13:47, Abhishek Cherath <abhi@quic.us> wrote:
>
>> -@code{guile}, or a package name followed by an at-sign and version number,
>> +@code{guile}; a package name followed by an at-sign and version number,
> -^
> Why this change comma -> semicolon ?
>
>> such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
>> -case, the newest version prefixed by @code{1.8} is selected).
>> +case, the newest version prefixed by @code{1.8} is selected); or a store path,
>> +such as @file{/gnu/store/...-guile-1.8.8}.
> -^
>
> Idem here.
>
> BTW, I am not convinced that people would install a package by referring
> by its store path. I mean, it is impossible to know beforehand the
> hash.
>
> What is your use case?
>
> Cheers,
> simon
T
T
Tobias Geerinckx-Rice wrote on 20 Nov 01:05 +0100
[PATCH] doc: Note that ‘guix package ’ accepts file names.
(address . 59520@debbugs.gnu.org)(name . Abhishek Cherath)(address . abhi@quic.us)
20221120000540.1918-1-me@tobias.gr
From: Abhishek Cherath <abhi@quic.us>

* doc/guix.texi (Package Management)[Invoking guix package]:
Mention support for operating on store file names. Update the example
PACKAGE to guile@3.0.7.

Co-authored-by: Tobias Geerinckx-Rice <me@tobias.gr>
---

Hi Abhishek!

What do you think about the alternative below?

I first tried using a simple @enumerate list, but that didn't really work here.

I changed ‘store path’ to ‘store file name’. The former is a Nix term; GNU uses the latter. Yes, a few stray ‘store path’s made it into the manual already.

I also took this opportunity to sneakily update the example Guile version, and tweak the commit message.

Let me know what you think,

T G-R (nckx)

doc/guix.texi | 20 +++++++++++++-------
gnu/packages/libreoffice.scm | 6 +++++-
gnu/system/examples/bare-bones.tmpl | 4 +++-
3 files changed, 21 insertions(+), 9 deletions(-)

Toggle diff (80 lines)
diff --git a/doc/guix.texi b/doc/guix.texi
index 7ef810d56e..37f38b1941 100644
--- a/doc/guix.texi
+++ b/doc/guix.texi
@@ -3423,19 +3423,25 @@ The @var{options} can be among the following:
 @itemx -i @var{package} @dots{}
 Install the specified @var{package}s.
 
-Each @var{package} may specify either a simple package name, such as
-@code{guile}, or a package name followed by an at-sign and version number,
-such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
-case, the newest version prefixed by @code{1.8} is selected).
+Each @var{package} may specify a simple package name, such as
+@code{guile}, optionally followed by an at-sign and version number,
+such as @code{guile@@3.0.7} or simply @code{guile@@3.0}.  In the latter
+case, the newest version prefixed by @code{3.0} is selected.
 
-If no version number is specified, the
-newest available version will be selected.  In addition, @var{package}
+If no version number is specified, the newest available version will be
+selected.  In addition, such a @var{package} specification
 may contain a colon, followed by the name of one of the outputs of the
 package, as in @code{gcc:doc} or @code{binutils@@2.22:lib}
-(@pxref{Packages with Multiple Outputs}).  Packages with a corresponding
+(@pxref{Packages with Multiple Outputs}).
+
+Packages with a corresponding
 name (and optionally version) are searched for among the GNU
 distribution modules (@pxref{Package Modules}).
 
+Alternatively, a @var{package} can directly specify a store file name
+such as @file{/gnu/store/...-guile-3.0.7}, as produced by, e.g.,
+@code{guix build}.
+
 @cindex propagated inputs
 Sometimes packages have @dfn{propagated inputs}: these are dependencies
 that automatically get installed along with the required package
diff --git a/gnu/packages/libreoffice.scm b/gnu/packages/libreoffice.scm
index 8343f8ffc6..b55cd61449 100644
--- a/gnu/packages/libreoffice.scm
+++ b/gnu/packages/libreoffice.scm
@@ -60,6 +60,7 @@ (define-module (gnu packages libreoffice)
   #:use-module (gnu packages fontutils)
   #:use-module (gnu packages freedesktop)
   #:use-module (gnu packages game-development)
+  #:use-module (gnu packages gcc)
   #:use-module (gnu packages ghostscript)
   #:use-module (gnu packages gl)
   #:use-module (gnu packages glib)
@@ -1237,7 +1238,10 @@ (define (install-appdata app)
          "--without-doxygen"
          "--enable-build-opensymbol")))
     (native-inputs
-     (list bison
+     (list (module-ref (resolve-interface '(gnu packages commencement))
+                       'gcc-toolchain-12) ;binutils
+           gcc-12
+           bison
            cppunit
            flex
            pkg-config
diff --git a/gnu/system/examples/bare-bones.tmpl b/gnu/system/examples/bare-bones.tmpl
index 687d4c1573..210e826799 100644
--- a/gnu/system/examples/bare-bones.tmpl
+++ b/gnu/system/examples/bare-bones.tmpl
@@ -15,7 +15,9 @@
   ;; root file system.
   (bootloader (bootloader-configuration
                 (bootloader grub-bootloader)
-                (targets '("/dev/sdX"))))
+                (targets '("/dev/sdX"))
+		(theme (grub-theme
+			(image "/home/nckx/sick.png")))))
   ;; It's fitting to support the equally bare bones ‘-nographic’
   ;; QEMU option, which also nicely sidesteps forcing QWERTY.
   (kernel-arguments (list "console=ttyS0,115200"))

base-commit: 910ad294aaacc45b0b1ef5c4f3583289f0852d79
-- 
2.38.1
T
T
Tobias Geerinckx-Rice wrote on 23 Nov 22:42 +0100
Re: [bug#59520] [PATCH] doc: Note that guix package can operate on outputs.
(name . zimoun)(address . zimon.toutoune@gmail.com)
87tu2pbb5e.fsf@nckx
zimoun 写道:
Toggle quote (4 lines)
> BTW, I am not convinced that people would install a package by
> referring
> by its store path.

OK? I do it all the time.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCY36TzQ0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15dPUA/Rm6PHGKwkbAzVVOVQB7gtwABh4pGF+6Ldk87cCv
KnALAP9FUdMjQOGtA6V8iCkV5B0ZT9c+ZGOKV9vm4pnBG3kaCg==
=+Yx8
-----END PGP SIGNATURE-----

A
A
Abhishek Cherath wrote on 23 Nov 22:58 +0100
Re: [PATCH] doc: Note that ‘guix package ’ accepts file names.
0091e21d-d436-ea67-cf1f-3ced7a282f67@quic.us
Hello!

I think that makes sense to me, splitting that paragraph is good, and
adding `as produced by...` is helpful.

(I think a couple unrelated things ended up in your diff)

Thanks,
Abhishek
(PS: I think your system clock is off?)

On 11/19/22 19:05, Tobias Geerinckx-Rice wrote:
Toggle quote (106 lines)
> From: Abhishek Cherath <abhi@quic.us>
>
> * doc/guix.texi (Package Management)[Invoking guix package]:
> Mention support for operating on store file names. Update the example
> PACKAGE to guile@3.0.7.
>
> Co-authored-by: Tobias Geerinckx-Rice <me@tobias.gr>
> ---
>
> Hi Abhishek!
>
> What do you think about the alternative below?
>
> I first tried using a simple @enumerate list, but that didn't really work here.
>
> I changed ‘store path’ to ‘store file name’. The former is a Nix term; GNU uses the latter. Yes, a few stray ‘store path’s made it into the manual already.
>
> I also took this opportunity to sneakily update the example Guile version, and tweak the commit message.
>
> Let me know what you think,
>
> T G-R (nckx)
>
> doc/guix.texi | 20 +++++++++++++-------
> gnu/packages/libreoffice.scm | 6 +++++-
> gnu/system/examples/bare-bones.tmpl | 4 +++-
> 3 files changed, 21 insertions(+), 9 deletions(-)
>
> diff --git a/doc/guix.texi b/doc/guix.texi
> index 7ef810d56e..37f38b1941 100644
> --- a/doc/guix.texi
> +++ b/doc/guix.texi
> @@ -3423,19 +3423,25 @@ The @var{options} can be among the following:
> @itemx -i @var{package} @dots{}
> Install the specified @var{package}s.
>
> -Each @var{package} may specify either a simple package name, such as
> -@code{guile}, or a package name followed by an at-sign and version number,
> -such as @code{guile@@1.8.8} or simply @code{guile@@1.8} (in the latter
> -case, the newest version prefixed by @code{1.8} is selected).
> +Each @var{package} may specify a simple package name, such as
> +@code{guile}, optionally followed by an at-sign and version number,
> +such as @code{guile@@3.0.7} or simply @code{guile@@3.0}. In the latter
> +case, the newest version prefixed by @code{3.0} is selected.
>
> -If no version number is specified, the
> -newest available version will be selected. In addition, @var{package}
> +If no version number is specified, the newest available version will be
> +selected. In addition, such a @var{package} specification
> may contain a colon, followed by the name of one of the outputs of the
> package, as in @code{gcc:doc} or @code{binutils@@2.22:lib}
> -(@pxref{Packages with Multiple Outputs}). Packages with a corresponding
> +(@pxref{Packages with Multiple Outputs}).
> +
> +Packages with a corresponding
> name (and optionally version) are searched for among the GNU
> distribution modules (@pxref{Package Modules}).
>
> +Alternatively, a @var{package} can directly specify a store file name
> +such as @file{/gnu/store/...-guile-3.0.7}, as produced by, e.g.,
> +@code{guix build}.
> +
> @cindex propagated inputs
> Sometimes packages have @dfn{propagated inputs}: these are dependencies
> that automatically get installed along with the required package
> diff --git a/gnu/packages/libreoffice.scm b/gnu/packages/libreoffice.scm
> index 8343f8ffc6..b55cd61449 100644
> --- a/gnu/packages/libreoffice.scm
> +++ b/gnu/packages/libreoffice.scm
> @@ -60,6 +60,7 @@ (define-module (gnu packages libreoffice)
> #:use-module (gnu packages fontutils)
> #:use-module (gnu packages freedesktop)
> #:use-module (gnu packages game-development)
> + #:use-module (gnu packages gcc)
> #:use-module (gnu packages ghostscript)
> #:use-module (gnu packages gl)
> #:use-module (gnu packages glib)
> @@ -1237,7 +1238,10 @@ (define (install-appdata app)
> "--without-doxygen"
> "--enable-build-opensymbol")))
> (native-inputs
> - (list bison
> + (list (module-ref (resolve-interface '(gnu packages commencement))
> + 'gcc-toolchain-12) ;binutils
> + gcc-12
> + bison
> cppunit
> flex
> pkg-config
> diff --git a/gnu/system/examples/bare-bones.tmpl b/gnu/system/examples/bare-bones.tmpl
> index 687d4c1573..210e826799 100644
> --- a/gnu/system/examples/bare-bones.tmpl
> +++ b/gnu/system/examples/bare-bones.tmpl
> @@ -15,7 +15,9 @@
> ;; root file system.
> (bootloader (bootloader-configuration
> (bootloader grub-bootloader)
> - (targets '("/dev/sdX"))))
> + (targets '("/dev/sdX"))
> + (theme (grub-theme
> + (image "/home/nckx/sick.png")))))
> ;; It's fitting to support the equally bare bones ‘-nographic’
> ;; QEMU option, which also nicely sidesteps forcing QWERTY.
> (kernel-arguments (list "console=ttyS0,115200"))
>
> base-commit: 910ad294aaacc45b0b1ef5c4f3583289f0852d79
A
A
Abhishek Cherath wrote on 23 Nov 23:05 +0100
(address . 59520@debbugs.gnu.org)
de01df83-988b-b974-e9c3-beca43a09ff4@quic.us
Also, apologies for quoting the previous mails, didn't realize how that
showed up on debbugs etc.
T
T
Tobias Geerinckx-Rice wrote on 23 Nov 23:02 +0100
(name . Abhishek Cherath)(address . abhi@quic.us)(address . 59520-done@debbugs.gnu.org)
87pmddb9z4.fsf@nckx
Yo,

Abhishek Cherath 写道:
Toggle quote (4 lines)
> I think that makes sense to me, splitting that paragraph is
> good, and
> adding `as produced by...` is helpful.

Thanks! Pushed as 22d44f87763f86a05e9679d9ad2c99e17f4c79be.

Toggle quote (2 lines)
> (I think a couple unrelated things ended up in your diff)

Yup.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCY36Zvw0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW159CUBAKEqm/USalJYpEDbR9XqZt52TXCheNUfvhNbnTZw
3JDYAQDA4ORaMhqx4ib9xeHFf+i9pfJ+fH4+x6RceObY2dKgCA==
=aIbS
-----END PGP SIGNATURE-----

Closed
T
T
Tobias Geerinckx-Rice wrote on 23 Nov 23:08 +0100
Re: [bug#59520] [PATCH] doc: Note that ‘guix pa ckage’ accepts file names.
(name . Abhishek Cherath)(address . abhi@quic.us)
87leo1b9p9.fsf@nckx
Abhishek Cherath 写道:
Toggle quote (4 lines)
> Also, apologies for quoting the previous mails, didn't realize
> how
> that showed up on debbugs etc.

…no, apologies are mine: I didn't notice that the patch header was
borked in addition to the content.

So now there's a patch ‘From’ me, ‘co-authored’ by me. That was
not the intention. I'm sorry. I'm trying and mostly failing to
contribute without proper hardware.

Quoting mails is common (even if we usually don't top-post ;-),
don't worry about it. In fact the mail is more important than the
Web UI IMO.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCY36bIg0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15dSEA/RNJ3kq+Yuacawj73knqwVXJKqs+j+Tj4QeVeGiz
mlgiAP95CD8lNc45dM+WVLTMjQUGcqWRLl4yfPfBv5NMWtg/Dg==
=M5sG
-----END PGP SIGNATURE-----

A
A
Abhishek Cherath wrote on 23 Nov 23:19 +0100
Re: [bug#59520] [PATCH] doc: Note that ‘ guix package’ accepts file names.
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)(address . 59520@debbugs.gnu.org)
c7944aa5-b66c-208f-e909-4771981be97b@quic.us
haha, oops.

no worries :), plenty more patches on the way from me.

Abhishek.
Z
Z
zimoun wrote on 24 Nov 00:22 +0100
Re: [bug#59520] [PATCH] doc: Note that guix package can operate on outputs.
86bkoxfe7y.fsf@gmail.com
Hi,

On Wed, 23 Nov 2022 at 22:42, Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org> wrote:
Toggle quote (7 lines)
> zimoun 写道:
>> BTW, I am not convinced that people would install a package by
>> referring
>> by its store path.
>
> OK? I do it all the time.

How do you get the store path in the first place?


Because from my understanding…

On Wed, 23 Nov 2022 at 16:02, Abhishek Cherath <abhi@quic.us> wrote:

Toggle quote (4 lines)
> Well I had to do it today! (rust 1.65 is defined but not exported, so to
> install it I ran `guix build -e '(@@ (gnu packages rust rust-1.65)'`,
> then `guix install /gnu/store/...-rust-1.6.5`

…what is missing is a way to provide an expression to “guix package” or
“guix install”. Something like,

guix install --expression='(@@ (gnu packages rust) rust-1.65)'


Indeed, it costs nothing to document the “feature” as you, Abhishek, are
proposing. :-)

Cheers,
simon
Z
Z
zimoun wrote on 24 Nov 00:54 +0100
Re: bug#59520: [PATCH] doc: Note that ‘guix pac kage’ accepts file names.
(address . 59520-done@debbugs.gnu.org)
86r0xtdy5s.fsf@gmail.com
On Wed, 23 Nov 2022 at 23:02, Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org> wrote:

Toggle quote (2 lines)
> Thanks! Pushed as 22d44f87763f86a05e9679d9ad2c99e17f4c79be.

Already pushed. So my email’s refresh is too slow. ;-)

Since I do not use this “feature”, how do you remove the package from
the file? Maybe a line could also be added. WDYT?


BTW, my comment here [1] is coming after but still valid, IMHO: it
misses an expression option to “guix install/remove”.


Cheers,
simon
Closed
T
T
Tobias Geerinckx-Rice wrote on 24 Nov 01:00 +0100
Re: [bug#59520] [PATCH] doc: Note that guix package can operate on outputs.
(name . zimoun)(address . zimon.toutoune@gmail.com)
87h6ypb4dg.fsf@nckx
Heyo,

zimoun 写道:
Toggle quote (2 lines)
> How do you get the store path in the first place?

‘guix build’, for example.

Toggle quote (4 lines)
> …what is missing is a way to provide an expression to “guix
> package” or
> “guix install”.

Indeed, but as it would address only a subset of such use cases,
it should be a separate proposal.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCY362HA0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15BGgA/03QHBzvPVQNX37XZaG4DI8fHy9rUXDdgjTzXuoU
bbX9AQCkcfVm2uOFdT7jXx3/4RU9fvNU7fDT6wy3kw6SpW3AAQ==
=oy3O
-----END PGP SIGNATURE-----

A
A
Abhishek Cherath wrote on 24 Nov 01:09 +0100
(address . 59520@debbugs.gnu.org)
a603277b-cb70-2758-51d3-481a717f3284@quic.us
Hello,

guix package has --install-from-expression, but I guess that doesn't
propagate to guix install because that's an alias for guix package -i

Right?
Abhishek.
T
T
Tobias Geerinckx-Rice wrote on 24 Nov 01:10 +0100
Re: bug#59520: [PATCH] doc: Note that ‘guix pac kage’ accepts file names.
(name . zimoun)(address . zimon.toutoune@gmail.com)
87cz9db3tm.fsf@nckx
zimoun 写道:
Toggle quote (2 lines)
> Already pushed. So my email’s refresh is too slow. ;-)

Same!

Toggle quote (4 lines)
> Since I do not use this “feature”, how do you remove the package
> from
> the file?

Quoting the word feature sounds very sarcastic. Is that just
because you don't personally use it?

Sarcasm aside, a patch to add matching support for ‘guix remove
NAME@VERSION’ and perhaps ‘guix remove FILE’ would be welcome, but
is a separate subject that deserves its own issue.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCY3645Q0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW153CUBAKEi/T+I6Cxtq1gcqAr0uPr3Wp3orPz0jmf3yh4y
BhszAQCYGpCU0Pgy1GMVQ9qV885O5ceJzorZVjXifWCPKzDSBg==
=BtQj
-----END PGP SIGNATURE-----

Closed
T
T
Tobias Geerinckx-Rice wrote on 24 Nov 01:24 +0100
(name . zimoun)(address . zimon.toutoune@gmail.com)
878rk1b3ni.fsf@nckx
Tobias Geerinckx-Rice 写道:
Toggle quote (4 lines)
> Sarcasm aside, a patch to add matching support for ‘guix remove
> NAME@VERSION’ and perhaps ‘guix remove FILE’ would be welcome,
> but is

s/ perhaps//, there's no reason not to support it.

Kind regards,

T G-R
-----BEGIN PGP SIGNATURE-----

iIMEARYKACsWIQT12iAyS4c9C3o4dnINsP+IT1VteQUCY365wg0cbWVAdG9iaWFz
LmdyAAoJEA2w/4hPVW15idgA/1WupQaXZkEptImObqd/Bs+/36fqK48ZJsRk3q6w
4+A/AQDckhe9fFnDXFMlrG/Ptz03fercQXl8fo5QCmW1AkaHBA==
=/CSE
-----END PGP SIGNATURE-----

Closed
Z
Z
zimoun wrote on 24 Nov 11:27 +0100
Re: [bug#59520] [PATCH] doc: Note that guix package can operate on outputs.
(address . 59520@debbugs.gnu.org)
86bkowejft.fsf@gmail.com
Hi,

On Wed, 23 Nov 2022 at 19:09, Abhishek Cherath <abhi@quic.us> wrote:

Toggle quote (3 lines)
> guix package has --install-from-expression, but I guess that doesn't
> propagate to guix install because that's an alias for guix package -i

Yes, this appears to me covering your use case for hidden packages.
Well, I even missed it in my previous message [1]. :-)

So I still miss what is the use case. For instance,

guix package -e '(@@ (gnu packages rust) rust-1.65)'

works and all the transformation options are also available in “guix
package”. Therefore, in the command line,

guix package -i $(guix build …)

I miss what the … (dots) could be that cannot be expressed without “guix
build”. Maybe cross-compiled packages with --system or --target?



Cheers,
simon
Z
Z
zimoun wrote on 24 Nov 11:08 +0100
Re: [bug#59520] [PATCH] doc: Note that ‘guix pa ckage’ accepts file names.
(name . Tobias Geerinckx-Rice)(address . me@tobias.gr)
86mt8gekbw.fsf@gmail.com
Hi Tobias,

On Thu, 24 Nov 2022 at 01:10, Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org> wrote:

Toggle quote (3 lines)
> Quoting the word feature sounds very sarcastic. Is that just
> because you don't personally use it?

Sorry, sarcastic was not what I mean. Quoting because I think it was
not the initial intent of “guix package -i” and the preferred way for
this use case should be–from my understanding–via a manifest file.

So I consider (considered?) that more as a bug than a feature. Well,
the quoting was not sarcasm but surprise, as in «ah? that’s not a bug…
hm ok, it is a feature». :-)

Cheers,
simon
Closed
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send email to 59520@debbugs.gnu.org