From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: www-plugins/gnash
Date: Thu, 30 Aug 2018 20:37:26 +0200 [thread overview]
Message-ID: <1535654246.1078.3.camel@gentoo.org> (raw)
In-Reply-To: <0d61b36b-88b0-4c3c-3a0f-5f8b9951fa81@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
On Thu, 2018-08-30 at 20:36 +0200, Chí-Thanh Christopher Nguyễn wrote:
> Michał Górny schrieb:
> > > So maybe mask it, but not remove?
> > >
> >
> > Maybe it's time you realize that if you want something to stay, then you
> > need to actually *take it* and *fix it*. Keeping clearly broken stuff
> > so that every user could try jumping through a few hoops to build it has
> > no value.
>
> I think it is a valid concern that removal of packages may sometimes be
> overzealous, and to better keep packages in the tree as long as they are
> useful and workarounds exist for build/runtime problems. Just in case of
> gnash there is really no benefit in keeping it.
>
It may make sense if there is some developer caring enough to actually
put those workarounds in the ebuild, rather than expecting every single
user trying to build it find them himself (and hope he's got all
of them, and the right set).
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
next prev parent reply other threads:[~2018-08-30 18:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-29 1:20 [gentoo-dev] Last rites: www-plugins/gnash Chí-Thanh Christopher Nguyễn
2018-08-29 9:01 ` Andrew Savchenko
2018-08-30 18:23 ` Chí-Thanh Christopher Nguyễn
2018-08-30 18:30 ` Michał Górny
2018-08-30 18:36 ` Chí-Thanh Christopher Nguyễn
2018-08-30 18:37 ` Michał Górny [this message]
2018-08-30 18:50 ` Chí-Thanh Christopher Nguyễn
-- strict thread matches above, loose matches on Subject: below --
2009-09-04 20:17 Rémi Cardona
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=1535654246.1078.3.camel@gentoo.org \
--to=mgorny@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