On 17/05/2018 07:53, Chris Marusich wrote:
Great article! Thank you for sharing it. The manual is nice, but I
have to admit, I enjoy reading these blog posts quite a bit, too. It's
nice to read a brief article that's focused on introducing a specific
aspect of Guix, with cross-references for
Every now and then, guix updates the list of substitutes. While doing
so, it displays a bunch of
substitute: updating list of substitutes from
'https://mirror.hydra.gnu.org'... 100.0%
Sometimes dozens of them in a row. I don't find it very informative to
show this to the user more tha
Chris Marusich writes:
>> A second question is, the contributor covenant has evolved, should we upgrade
>> ours from 1.3.0 to the current
>> [1.4.0](https://www.contributor-covenant.org/version/1/4/code-of-conduct)?
>
> To help people understand what has changed going from 1.3.0 to 1.4, here
> is
l...@gnu.org (Ludovic Courtès) writes:
> Hello Guix!
>
> On ‘guix pack -R’:
>
>
> https://www.gnu.org/software/guix/blog/2018/tarballs-the-ultimate-container-image-format/
>
> Enjoy! :-)
Great article! Thank you for sharing it. The manual is nice, but I
have to admit, I enjoy reading these
On Wed, May 16, 2018 at 10:22:27PM -0700, Chris Marusich wrote:
> The LibreOffice version scheme is described here:
>
> https://wiki.documentfoundation.org/ReleasePlan#Version_scheme
>
> It looks like version 5.4.7.2 is supposed to be the 2nd release
> candidate of the 7th bugfix release in the 5
Hi,
I did a "guix pull" today and found out that I couldn't build my profile
because the source for LibreOffice 5.4.7.1 is missing. It seems to have
been removed from the various mirrors. I've fixed the LibreOffice
problem by bumping the libreoffice package to 5.4.7.2 in commit
7376ba4cd4d07b564
Hi Katherine,
Katherine Cox-Buday writes:
> Pjotr Prins writes:
>
>>> Not packaging FF or crippling FF is a no-go! Doing so will discourage
>>> users from using GuixSD and Free Software.
>
> As an anecdote with a data-point of one, I uninstalled GuixSD because I
> suddenly needed the machine I
Oleg Pykhalov writes:
> I understand this, but still you could use almost all Guix stuff
> except Shepherd system services [1] on a foreign distribution. Guix
> works smoothly for me on a working computer with GNU/Linux Mint on a
> board, and I use GuixSD on my personal computer and laptop. Also
Hello Katherine,
Katherine Cox-Buday writes:
> Pjotr Prins writes:
[…]
> As an anecdote with a data-point of one, I uninstalled GuixSD because I
> suddenly needed the machine I was running it on to be my daily driver. I
> had been attempting to package Firefox whenever I had a spare moment,
>
Katherine Cox-Buday writes:
> Pjotr Prins writes:
>
>>> Not packaging FF or crippling FF is a no-go! Doing so will discourage
>>> users from using GuixSD and Free Software.
>
> As an anecdote with a data-point of one, I uninstalled GuixSD because I
> suddenly needed the machine I was running it o
Tonton writes:
> I guess channels already sort of exist. have a git repo or similar with
> whatever guix packages in it and point $GUIX_PACKAGE_PATH at it. Then all
> packages defined in your git repo are suddenly part of your available guix
> packages.
I agree this is an option; however, I thin
Gábor Boskovits writes:
> There was a bug in earlier Firefox, might that be that IceCat doesn't have
> the fix for that yet? I don't know how much IceCat is delayed to Firefox.
> https://stackoverflow.com/questions/24573061/uncaught-syntaxerror-in-strict-mode-code-functions-can-only-be-declared-at
On Wed, 16 May 2018 15:14:45 +
Nils Gillmann wrote:
>
> For the website, I have a sxml version of this CoC version. You'd need
> to check which words I added in (I added 3 or 4 extra words I think), but
> if you want to link to it on the website or even include it, could that
> be useful?
>
I guess channels already sort of exist. have a git repo or similar with
whatever guix packages in it and point $GUIX_PACKAGE_PATH at it. Then all
packages defined in your git repo are suddenly part of your available guix
packages.
On Wed, 16 May 2018 10:44:20 -0500
Katherine Cox-Buday wrote:
> P
I realize as I finish writing, I've created a wall of text. Maybe more than
you bargained for.
:)
On Wed, 16 May 2018 16:06:07 +0100
ra...@airmail.cc wrote:
> For the section about IRC. Please add a bit that explains why you
> shouldn't say "hi guys" when you join IRC. Instead "Hi guix" or "H
Pjotr Prins writes:
>> Not packaging FF or crippling FF is a no-go! Doing so will discourage
>> users from using GuixSD and Free Software.
As an anecdote with a data-point of one, I uninstalled GuixSD because I
suddenly needed the machine I was running it on to be my daily driver. I
had been att
Tonton transcribed 3.8K bytes:
> I realize as I'm updating the CoC in the source and adding it to the info
> docs, that the original introduction from contributing was much nicer. It
> has a positive focus. Should I change the paragraf under to use
> something like the following from contributing:
For the section about IRC. Please add a bit that explains why you
shouldn't say "hi guys" when you join IRC. Instead "Hi guix" or "Hi
#guix" is recommended.
Original Message
Subject: [PATCH] website: Add section section and links to code of
conduct
Date: 2018-05-16 00:36
Fr
Ludovic Courtès transcribed 173 bytes:
> Hello Guix!
>
> On ‘guix pack -R’:
>
>
> https://www.gnu.org/software/guix/blog/2018/tarballs-the-ultimate-container-image-format/
>
> Enjoy! :-)
>
> Ludo’.
>
Nice!
Nitpick: You technically require tar + gzip for the code in the example, which
is
Amazing work, thank you so much!
--
Pierre Neidhardt
signature.asc
Description: PGP signature
Hello Guix!
On ‘guix pack -R’:
https://www.gnu.org/software/guix/blog/2018/tarballs-the-ultimate-container-image-format/
Enjoy! :-)
Ludo’.
21 matches
Mail list logo
