From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: 30566@debbugs.gnu.org
Subject: bug#30566: While searching for packages, deprecated packages should be ignored
Date: Wed, 21 Feb 2018 10:03:16 +0100 [thread overview]
Message-ID: <20180221100316.42ccce5f@alma-ubu> (raw)
When I search for a deprecated package, I get both the deprecated
package and the new one. That is quite confusing and I can't decide
which one to take. For example:
$ guix package -s geiser
name: geiser-next
version: 0.9
outputs: out
systems: x86_64-linux i686-linux armhf-linux aarch64-linux
mips64el-linux dependencies: emacs-minimal-25.3 guile-2.0.14
location: guix/packages.scm:335:2
homepage: https://nongnu.org/geiser/
license: Modified BSD
synopsis: Collection of Emacs modes for Guile and Racket hacking
description:
[..]
relevance: 6
name: geiser
version: 0.9
outputs: out
systems: x86_64-linux i686-linux armhf-linux aarch64-linux
mips64el-linux dependencies: emacs-minimal-25.3 guile-2.0.14
location: gnu/packages/emacs.scm:314:2
homepage: https://nongnu.org/geiser/
license: Modified BSD
synopsis: Collection of Emacs modes for Guile and Racket hacking
description:
[..]
relevance: 6
Here I get two exactly same results, besides the package name and the
source code line number.
I have to look into the package sources to find out which of the two is
the not-deprecated one.
As a user, I would like to see only the new package mentioned. Maybe
some users also want a short note like:
"geiser formerly known as geiser-new."
Technical background:
`deprecated-package` is defined in `guix/packages.scm`:
```
(define (deprecated-package old-name p)
"Return a package called OLD-NAME and marked as superseded by P, a package
object."
(package
(inherit p)
(name old-name)
(properties `((superseded . ,p)))))
```
That means the `guix package -s` should somehow make use of the
`superseeded` property.
Björn
next reply other threads:[~2018-02-21 9:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 9:03 Björn Höfling [this message]
2018-02-27 14:49 ` bug#30566: While searching for packages, deprecated packages should be ignored 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180221100316.42ccce5f@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=30566@debbugs.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.