unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 29973@debbugs.gnu.org
Subject: [bug#29973] [PATCH] gnu: newsbeuter: Supersede.
Date: Mon, 08 Jan 2018 00:13:40 +0100	[thread overview]
Message-ID: <87wp0tdzyz.fsf@gnu.org> (raw)
In-Reply-To: <11e8b12c-4ab6-002e-6956-90cd5f7f6a36@tobias.gr> (Tobias Geerinckx-Rice's message of "Thu, 4 Jan 2018 20:42:29 +0100")

Heya!

Tobias Geerinckx-Rice <me@tobias.gr> skribis:

> What I meant to say was: there might be a better way to do this than a
> 100-line patch, but this is the best I can come up with.
>
> I don't really understand why
>
>   (define-public foo (package ... (inputs `(("bar" ,bar)))))
>   (define-public bar ...)
>
> appears to work, while
>
>   (define-public foo (package ... (properties `((superseded . ,bar)))))
>   (define-public bar ...)
>
> seems to fail.

Indeed.

Unless you really want to keep the ‘newsbeuter’ definition around, you
can also simply:

  (define-public newsbeuter
    (deprecated-package "newsbeuter" newswhatever))

The only value in keeping the old definition is that power users can
still install it with “guix build -e”.

My 2¢,
Ludo’.

  reply	other threads:[~2018-01-07 23:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04  2:21 [bug#29973] [PATCH] gnu: newsbeuter: Supersede Tobias Geerinckx-Rice
2018-01-04  2:59 ` Leo Famulari
2018-01-04 14:54   ` Tobias Geerinckx-Rice
2018-01-04 17:34     ` Leo Famulari
2018-01-04 19:22       ` ng0
2018-01-04 19:23       ` ng0
2018-01-04 19:42       ` Tobias Geerinckx-Rice
2018-01-07 23:13         ` Ludovic Courtès [this message]
2018-01-08 13:48           ` Tobias Geerinckx-Rice
2018-01-11  2:17 ` bug#29973: " Tobias Geerinckx-Rice

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=87wp0tdzyz.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=29973@debbugs.gnu.org \
    --cc=me@tobias.gr \
    /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).