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

[Abhishek Cherath <abhi@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:
> 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