From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>,
"Guix Devel" <guix-devel@gnu.org>,
"Mathieu Othacehe" <othacehe@gnu.org>
Subject: Re: Release progress, week 8
Date: Sun, 04 Dec 2022 00:32:11 -0500 [thread overview]
Message-ID: <877cz77mzo.fsf@gmail.com> (raw)
In-Reply-To: <86bkok3iii.fsf@gmail.com> (zimoun's message of "Sat, 03 Dec 2022 11:10:13 +0100")
Hi Simon,
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Ludo,
>
> On Fri, 02 Dec 2022 at 23:45, Ludovic Courtès <ludo@gnu.org> wrote:
>
>> I started writing super long release notes (a book!), comments welcome:
>>
>> https://git.savannah.gnu.org/cgit/guix/guix-artwork.git/tree/website/drafts/gnu-guix-1.4.0-released.md
>>
>> Comments? Suggestions? Happiness? Excitement? You tell!
Thank you for writing it! It looks good, though I think the explanation
of the benefit of GUIX_PYTHONPATH is a bit backward; one of the main
goals was to avoid having foreign distributions break spectacularly
because of Guix exposing their (sometimes incompatible) Python libraries
via the shared PYTHONPATH. It also fixed a sometimes useful use case of
using Python's virtualenv on top of Guix.
[...]
> About “guix pack -f deb”, I thought it was experimental and it is not
> mentioned. Maybe,
I don't think there's a need to label it as experimental. The mechanics
are simple, and already proven to work. I don't see the user-facing
options changing in backward incompatible ways in the future.
> —has
> been extended with an experimental format: `guix pack -f deb` creates a
> standalone `.deb` package
>
> It reminds me that,
>
> https://othacehe.org/wsl-images-for-guix-system.htm
>
> could fit a Guix blog post. Mathieu, WDYT?
Mathieu wrote one already, it's published on their personal blog. I've
read it recently, it was interesting [0]
[0] https://othacehe.org/wsl-images-for-guix-system.html
> About the part « **Python packaging** has seen important changes. » I
> would mention the removal of many Python 2 packages. Maxim, WDYT?
It's already mentioned in the NEWS which will land in the announcement
emails, at least. We could mention that despite removing 500+ Python 2
packages, our collection has grown from X to Y ;-).
I'll see if I can squeeze some extra bits in before the release.
--
Thanks,
Maxim
next prev parent reply other threads:[~2022-12-04 5:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 22:45 Release progress, week 8 Ludovic Courtès
2022-12-02 23:48 ` Vagrant Cascadian
2022-12-03 17:53 ` Ludovic Courtès
2022-12-04 1:55 ` missing sanity check Vagrant Cascadian
2022-12-03 10:10 ` Release progress, week 8 zimoun
2022-12-04 5:32 ` Maxim Cournoyer [this message]
2022-12-04 10:38 ` zimoun
2022-12-05 14:43 ` Ludovic Courtès
2022-12-03 17:55 ` Julien Lepiller
2022-12-05 14:44 ` Ludovic Courtès
2022-12-04 12:06 ` Mathieu Othacehe
2022-12-06 14:32 ` Ludovic Courtès
2022-12-07 9:34 ` Mathieu Othacehe
2022-12-06 16:51 ` 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877cz77mzo.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=othacehe@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).