unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 22628@debbugs.gnu.org
Subject: bug#22628: Emacs: ^ in installed package list misses some upgrades
Date: Fri, 12 Feb 2016 22:29:34 +0300	[thread overview]
Message-ID: <87si0x3ext.fsf@gmail.com> (raw)
In-Reply-To: <87r3gi11j5.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 12 Feb 2016 14:49:50 +0100")

Ludovic Courtès (2016-02-12 16:49 +0300) wrote:

> Alex Kost <alezost@gmail.com> skribis:
>
>> The fact that we have 2 versions is the answer.  In Emacs UI a package
>> is not considered to be obsolete if there is a package definition with
>> the same name+version.
>>
>> That's why "texinfo 6.0" is green in the list, not red (as obsolete
>> packages).
>
> Oh, to me, ^ meant “upgrade”, like ‘guix package -u’ but only taking
> into account the version number (‘guix package -u’ upgrades if the store
> file name differs, even if the version number is the same.)

OK, you can still mark it for upgrading using "U" key.  If you don't mind
I wouldn't like to change the current behavior (at least now) :-)

>> I believe marking such packages as obsolete is not correct and it may be
>> confusing.  See <https://gnunet.org/bot/log/guix/2016-02-09#T909651>.
>
> I think we need a different solution for packages that have several
> series.  For instance, we could have:
>
>   (define gnupg-2.0
>     (package …
>       (properties `((series . "2.0")))))
>
> and that would lead the various UIs to upgrade only to a package whose
> version prefix is “2.0”.
>
> WDYT?

Yeah, this looks like a great solution for such issues!

-- 
Alex

  parent reply	other threads:[~2016-02-12 19:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11  9:11 bug#22628: Emacs: ^ in installed package list misses some upgrades Ludovic Courtès
2016-02-12 10:40 ` Alex Kost
2016-02-12 13:49   ` Ludovic Courtès
2016-02-12 14:01     ` Andreas Enge
2016-02-12 19:29     ` Alex Kost [this message]
2019-12-02 17:54 ` bug#22628: Bug #22628 Hunting: " zimoun
2019-12-02 23:03   ` Ludovic Courtès
2019-12-05 17:22     ` zimoun

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=87si0x3ext.fsf@gmail.com \
    --to=alezost@gmail.com \
    --cc=22628@debbugs.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 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).