Ricardo Wurmus writes:
> Ludovic Courtès writes:
>
>> Hello,
>>
>> I think “Guix System” is OK.
>
> I think so too.
I recommend against renaming GuixSD >> "Guix System". Here is Why:
1) A noob would expect "guix system" to refer to the whole Guix
enchilada. If we use it to refer to GuixSD,
Hi,
Ludovic Courtès writes:
> Hello,
>
> Pierre Neidhardt skribis:
>
>> - If we get started with Guix CI and Guix OS, I'm afraid that soon enough we
>> will end up with a bunch Guix FS, Guix IP, Guix CD...
>
> I think “Guix System” is OK. Most of the time we’ll just say “Guix”, as
> is
ISTM our doc is a veritable "Profile Blizzard."
The term occurs 173 times in guix.texi
The "user profile" is referred to in multiple ways:
(guix) Application Setup: "your Guix profile"
(guix) Features: 'own “profile”', "per-user profiles", "their profile"
(guix) Invoking guix package:
Ludovic Courtès writes:
> Hi George,
>
> George Clemmer skribis:
>
>> ISTM we can improve this situation as follows:
>>
>> 1) agree on a canonical term to use for the 4 types of profiles
>
> I think you mentioned only two types of “profiles”: one is
Hi Nils,
Nils Gillmann writes:
> 4) before each profile kind is used for the first time,
> make use of something like this for the brief introduction
> of it again (our manual is not very long, but it is still
> long):
I Agee.
> @cartouche
> @quotation Note
> In the following
Alex Kost writes:
> "M-x guix" can't be an entry point for this or any other interface, it
> is only for "guix" *shell* commands. Actually I'm very surprised
> someone uses "M-x guix", I find it unpractical.
Agreed. FWIW, when I am trying to find an emacs-guix command I type 'M-x
guix-' and
Hello
Ricardo Wurmus writes:
> Hello Mathieu,
>
>> Mathieu Lirzin skribis:
>>
>>> Following the announcement made by RMS regarding the new GNU Kind
>>> Communication Guidelines (GKCG) [1], I would like to know if the Guix
>>> developpers in particular its maintainers would agree to adopt it in
Hi Ludo’,
Ludovic Courtès writes:
> Hello,
>
> George Clemmer skribis:
>
>> YOANN hit an error when trying to do 'guix package -m
>> ~/.guix-profile/manifest'. Why would one want to do this? Maybe to
>> (re)produce a configuration previously reached by a
Ricardo Wurmus writes:
> Hi George,
>
>> My thinking is that if there was an easy way to produce “manifests as
>> passed to ‘guix package -m’” from profiles, it would be a handy: an easy
>> way for someone that has gone down the incremental path to switch to
>> manifests and an easy way to
Ludovic Courtès writes:
> Hello,
>
> Ricardo Wurmus skribis:
>
[...]
>> You can put this in a file “manifest-to-manifest.scm” and run it like
>> this from a Guix source checkout:
>>
>> ./pre-inst-env guile -s manifest-to-manifest.scm /path/to/.guix-profile
>> > my-manifest.scm
>
> I like
This LGTM except ... the first paragraphs (quoted below) are an
advertisement. This is out of place in a tutorial. So, IMO, they should
simply be removed.
> GNU Guix stands out as the *hackable* package manager, mostly because
> it uses [GNU Guile](https://www.gnu.org/software/guile/), a
Ludovic Courtès writes:
> Hello,
>
> YOANN P skribis:
>
>> I was thinking than "~/.guix-profile/manifest" was a valid manifest file due
>> to his name, but it seems not that is the case from the error i've got
>>
>> https://pastebin.com/Z7h2t5mL
>>
>> After some search , i've finally
Gábor Boskovits writes:
> George Clemmer ezt írta (időpont: 2018. aug. 30., Cs,
> 21:14):
>
>>
>> Ricardo Wurmus writes:
>>
>> > Ludovic Courtès writes:
>> >
>> >> Hello,
>> >>
>> >> I think “Guix System” is
Hi Lprndn,
I am glad to see your interest in these issues.
Ludovic Courtès writes:
> Hi,
>
> L p R n d n skribis:
>
>> Ludovic Courtès writes:
>
> [...]
>
>>> A very concrete task that could be of interest to you is the “name
>>> change” (a bit of a strong word) that we’d like to
swedebu...@riseup.net writes:
> First of all thanks for building a great OS!
+1
> In my view we still have a system where encountering a bug is still far
> more common than any other OS I ever used.
+1
> To sum it up: lets not ruin what we have by rushing ahead and ending
> beta too early.
+1
Hi Gavin,
Gavin Smith writes:
[...]
> A manual with this interface added is at
> https://www.gnu.org/software/texinfo/manual/texinfo-html/Overview.html.
> All the important keyboard commands that work in the Info viewers are
> implemented, including index lookup.
Nice! I like seeing Info
Hello!
elaexuo...@wilsonb.com writes:
> FWIW, I never expected `/manifest' to encode "this is what the user
> ordered," so much as "this is the recipe for (deterministically) reproducing
> this exact profile." For the former we have `packages->manifest',
> `specifications->manifest' etc. The
Hi zimoun,
zimoun writes:
> In contradiction with what I wrote above, I agree. :-)
>
> /manifest should be renamed /specifications or
> something like that.
>
> And a comment could be inserted in this file saying: internal usage, do
> not modify, etc..
>
> WDYT?
Sure, that would work. But,
Ludovic Courtès writes:
> elaexuo...@wilsonb.com skribis:
>> First, am I missing something? Is there a better/preferred way to make use of
>> the `manifest' files in profiles?
> You’re not missing anything: it’s a longstanding source of confusion
> that these ‘manifest’ files are not like
zimoun writes:
> (from: http://issues.guix.gnu.org/issue/41253#10)
>
> On Fri, 5 Jun 2020 at 18:36, Ludovic Courtès wrote:
>
>> > There are many examples in guix.texi with $, and also many without. Plus
>> > some with # as the command line prompt.
>> I’ve come to the conclusion that snippets
20 matches
Mail list logo
