From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Dealing with interface deprecation
Date: Thu, 07 Oct 2021 22:26:33 -0400 [thread overview]
Message-ID: <87y2742qw6.fsf@gmail.com> (raw)
In-Reply-To: <87r1d8amce.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 28 Sep 2021 14:58:09 +0200")
Hello!
Ludovic Courtès <ludo@gnu.org> writes:
> Hello Guix!
>
> In Guix, configuration is code, which is great! But that also means
> users occasionally have to deal with things like “API deprecation”,
> which never sounds exciting, especially when all you want is to get your
> system upgraded Right Now.
>
> So I think it’s important to be very careful in how we deal with API
> deprecation, in particular in Guix System (and in Guix Home once we’ve
> removed the “technology preview” label).
>
> There were two examples where, with my “regular user” hat on (which I
> particularly enjoy), I got deprecation messages that were not actionable
> for me because they lacked source location info. This was addressed by
> these changes:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit?id=e0bd47b4fd5eb009f34004242e16b976e58756b0
> https://git.savannah.gnu.org/cgit/guix.git/commit?id=baf4272df2350a40bfa198f5cdb42e707e32ad71
>
> As you can see, providing good actionable messages for record field
> deprecation is a bit of a craft, but hopefully that gives an idea of how
> to get there; maybe we’ll eventually come up with a high-level way to
> express that.
>
> Packages may also be part of the “API”. On ‘core-updates’, several TeX
> Live packages were deprecated but still used because there wasn’t any
> warning. This is how I addressed it:
>
> https://git.savannah.gnu.org/cgit/guix.git/commit?id=3dc8052b51241fe7857059d3300dad3a0f9f68fd
>
> Thoughts? Tips and tricks?
Wow! Thanks a lot for sharing these tips on the art of making better
deprecation! I'll keep these commits bookmarked for the next time :-).
Maxim
prev parent reply other threads:[~2021-10-08 2:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 12:58 Dealing with interface deprecation Ludovic Courtès
2021-10-08 2:26 ` Maxim Cournoyer [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2742qw6.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.