From: Raymond Jennings <shentino@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] removal of bopm before hopm is in tree
Date: Thu, 25 Aug 2016 19:29:35 -0700 [thread overview]
Message-ID: <CAGDaZ_rGg_tiB5B4Am1HpvS2AFdVRhh-GZCoo4NFORGVw4KbYA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 375 bytes --]
I still use bopm, and it built fine last time I emerged it.
If hopm isn't in the tree yet, why was bopm still pmasked for removal?
Reason for asking is I'm curious about removal procedures. I was under the
impression that replacement packages get added to the tree before their
obsolete predecessors get pmasked for booting out.
And if that's not the case, should it be?
[-- Attachment #2: Type: text/html, Size: 482 bytes --]
next reply other threads:[~2016-08-26 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 2:29 Raymond Jennings [this message]
2016-08-26 13:43 ` [gentoo-user] removal of bopm before hopm is in tree Michael Mol
2016-08-30 22:18 ` Raymond Jennings
2016-08-30 22:26 ` Raymond Jennings
2016-08-28 6:40 ` Daniel Campbell
2016-08-28 16:45 ` P Levine
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=CAGDaZ_rGg_tiB5B4Am1HpvS2AFdVRhh-GZCoo4NFORGVw4KbYA@mail.gmail.com \
--to=shentino@gmail.com \
--cc=gentoo-user@lists.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