From: Ulrich Mueller <ulm@gentoo.org>
To: Michael Orlitzky <mjo@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 0/3] elisp{,-common}.eclass update for emacs-vcs consolidation
Date: Wed, 18 Dec 2019 17:34:30 +0100 [thread overview]
Message-ID: <w6gtv5xpp7t.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <3002c804-e70f-5b50-ee38-d91aa7e22fb0@gentoo.org> (Michael Orlitzky's message of "Wed, 18 Dec 2019 07:19:17 -0500")
[-- Attachment #1: Type: text/plain, Size: 747 bytes --]
>>>>> On Wed, 18 Dec 2019, Michael Orlitzky wrote:
>> No revbumps will be done for this (and virtual/emacs will be simply
>> removed without prior masking).
> I guess it's nice that we know ahead of time, but is there any reason
> to suspect that this won't cause havoc?
Removal of the virtual/emacs ebuilds won't remove the installed package
from users' systems. It will eventually disappear, when all its reverse
dependencies have been updated. Why would its continued presence as an
installed package (for another while) cause any problems?
Revbumping its more than 400 reverse dependencies really doesn't sound
so attractive, and would cause rebuilds on users' systems for virtually
(pun intended :-) no benefit.
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-12-18 16:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 11:08 [gentoo-dev] [PATCH 0/3] elisp{,-common}.eclass update for emacs-vcs consolidation Ulrich Müller
2019-12-18 11:08 ` [gentoo-dev] [PATCH 1/3] elisp-common.eclass: Allow full versions in elisp-need-emacs() Ulrich Müller
2019-12-18 11:08 ` [gentoo-dev] [PATCH 2/3] elisp-common.eclass: Update documentation Ulrich Müller
2019-12-18 11:08 ` [gentoo-dev] [PATCH 3/3] elisp.eclass: Depend on app-editors/emacs directly Ulrich Müller
2019-12-18 11:47 ` [gentoo-dev] [PATCH 0/3] elisp{,-common}.eclass update for emacs-vcs consolidation Michał Górny
2019-12-18 12:01 ` Ulrich Mueller
2019-12-18 12:19 ` Michael Orlitzky
2019-12-18 16:34 ` Ulrich Mueller [this message]
2019-12-18 23:28 ` Michael Orlitzky
2019-12-20 1:19 ` Michael Orlitzky
2019-12-21 6:57 ` Ulrich Mueller
2019-12-21 11:27 ` Michael Orlitzky
2019-12-21 11:39 ` Ulrich Mueller
2019-12-21 11:41 ` Michael Orlitzky
2019-12-21 11:50 ` Ulrich Mueller
2019-12-21 11:49 ` Michael Orlitzky
2019-12-21 11:52 ` Ulrich Mueller
2019-12-21 13:31 ` Michael 'veremitz' Everitt
2019-12-20 13:43 ` [gentoo-dev] [PATCH v2 1/3] elisp-common.eclass: New function elisp-check-emacs-version Ulrich Müller
2019-12-20 13:43 ` [gentoo-dev] [PATCH v2 2/3] elisp-common.eclass: Update documentation Ulrich Müller
2019-12-20 13:44 ` [gentoo-dev] [PATCH v2 3/3] elisp.eclass: Depend on app-editors/emacs directly Ulrich Müller
2019-12-20 22:10 ` Ulrich Mueller
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=w6gtv5xpp7t.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mjo@gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox