public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mart Raudsepp <leio@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: app-misc/toilet
Date: Sun, 17 Nov 2019 11:30:03 +0200	[thread overview]
Message-ID: <3b073ed82c22a4df6f5b2c1e1058e2cb30344f12.camel@gentoo.org> (raw)
In-Reply-To: <20191117020710.GG6848@bubba.lan>

[-- Attachment #1: Type: text/plain, Size: 959 bytes --]

Ühel kenal päeval, L, 16.11.2019 kell 21:07, kirjutas Aaron Bauman:
> On Sat, Nov 16, 2019 at 08:29:58PM -0500, Aaron Bauman wrote:
> > # Aaron Bauman <bman@gentoo.org> (2019-11-16)
> > # EAPI=4. --filter=gay Really?!
> > # Removal in 15 days
> > app-misc/toilet
> > 
> > -- 
> > Cheers,
> > Aaron
> 
> Add the following as it is an rdep
> 
> net-irc/rbot

Why are you last-riting packages that some team does maintain without
any apparent talk with them (unless I simply fail to find an ack),
purely because it happens to have a local USE flag to very much
optionally depend on that app-misc/toilet as an alternative to figlet?
So even with this gone, it would retain such optional feature
functionality via USE=figlet.

There's also no bug reference for people to give feedback or updates
on, as is customary (or even required, can't remember) for last rites.

Also would appreciate better worded last-rite reasoning..


Mart

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

  parent reply	other threads:[~2019-11-17  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17  1:29 [gentoo-dev] Last rites: app-misc/toilet Aaron Bauman
2019-11-17  2:07 ` Aaron Bauman
2019-11-17  4:34   ` Michael 'veremitz' Everitt
2019-11-17  9:30   ` Mart Raudsepp [this message]
2019-11-17 12:22 ` rudi
2019-11-17 13:08   ` 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=3b073ed82c22a4df6f5b2c1e1058e2cb30344f12.camel@gentoo.org \
    --to=leio@gentoo.org \
    --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