unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Potential minor API change notice
Date: Fri, 02 Dec 2022 10:06:01 +0100	[thread overview]
Message-ID: <871qpiw4xy.fsf@gnu.org> (raw)
In-Reply-To: <87a649k93x.fsf@gmail.com> (Maxim Cournoyer's message of "Tue, 29 Nov 2022 11:40:02 -0500")

Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> Hi,
>>
>> Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
>>
>>> This is a heads up to let you know that the
>>> %BASE-PACKAGES-DISK-UTILITIES public variable exported from (gnu system)
>>> may be removed in the near future.
>>
>> If the patch eventually gets consensus, I would suggest making that
>> variable an alias using ‘define-deprecated’: that way people will know
>> about it and code won’t break.
>
> An deprecated alias to what?

To ‘%base-packages’ for example?  It doesn’t really matter.

What’s important is to never ever remove a public variable, or change
the signature of a public procedure, without prior deprecation period
(at least for interfaces that one may use in their System or Home config
files.)

gnu/{services,packages}/*.scm contain bindings that have been deprecated
for years.  That’s probably excessive, but lack of a deprecation period
would unnecessarily upset fellow users and then we’d have to channel
their anger.  :-)

Ludo’.


  reply	other threads:[~2022-12-02  9:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-28 20:07 Potential minor API change notice Maxim Cournoyer
2022-11-29  9:02 ` Ludovic Courtès
2022-11-29 16:40   ` Maxim Cournoyer
2022-12-02  9:06     ` Ludovic Courtès [this message]
2022-12-04  4:44       ` Maxim Cournoyer
2022-12-05 16:19 ` Katherine Cox-Buday
2022-12-05 19:29   ` Maxim Cournoyer

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=871qpiw4xy.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=maxim.cournoyer@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).