From: "Dustin C. Hatch" <admiralnemo@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Package removal without proper last-riting
Date: Mon, 11 Nov 2013 17:55:07 -0600 [thread overview]
Message-ID: <52816E5B.4050706@gmail.com> (raw)
In-Reply-To: <20131111135122.4f6740ea@TOMWIJ-GENTOO>
On 11/11/2013 06:51, Tom Wijsman wrote:
> On Mon, 11 Nov 2013 10:47:30 +0100
> Michał Górny <mgorny@gentoo.org> wrote:
>
>> Silent removals do us no good.
...
>
> 1) dev-only seems to be the main cause of lost announcements, which
> isn't that worry some as most of us still receive them but it would
> be nice for them to be in dev-announce as well;
This is actually the reason I subscribed to -dev in the first place. I
started noticing that some packages I needed/used/used to use/etc. were
being removed and I wanted to find out why. At first, I subscribed to
-announce and -dev-announce, but I found that I still wasn't being notified.
I know overlays aren't officially supported, but the courtesy of
announcing package removals, especially libraries, would be much
appreciated. There have been times that a library I use for an internal
project, for example, was removed without notice, forcing me to look at
the CVS attic to find out why. More often than not, though, the commit
message is simply "removed" or "clean up," which is just as unhelpful.
While I have no problem copying stuff back out of the attic into a local
overlay, it would be nice to prepare for that before something breaks.
Thank you,
--
♫Dustin
http://dustin.hatch.name/
next prev parent reply other threads:[~2013-11-11 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 9:32 [gentoo-dev] Package removal without proper last-riting Manuel Rüger
2013-11-11 9:38 ` Sergey Popov
2013-11-11 9:47 ` Michał Górny
2013-11-11 12:51 ` Tom Wijsman
2013-11-11 14:49 ` Thomas Kahle
2013-11-11 23:55 ` Dustin C. Hatch [this message]
2013-11-12 6:22 ` Sergey Popov
2013-11-14 3:08 ` [gentoo-dev] " Ryan Hill
2013-11-14 19:45 ` Diego Elio Pettenò
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=52816E5B.4050706@gmail.com \
--to=admiralnemo@gmail.com \
--cc=gentoo-dev@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