public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Chí-Thanh Christopher Nguyễn" <chithanh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: www-plugins/gnash
Date: Thu, 30 Aug 2018 20:50:51 +0200	[thread overview]
Message-ID: <051805c4-1b8a-b887-09b5-106e3604b54f@gentoo.org> (raw)
In-Reply-To: <1535654246.1078.3.camel@gentoo.org>

Michał Górny schrieb:
>> 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).

If you mean, putting these workarounds as elog message, maybe.
But putting them as code is not always possible, as it may require changes in 
other packages or similar.
And sometimes, there were building and working packages masked for removal 
just because they lacked a maintainer.


Best regards,
Chí-Thanh Christopher Nguyễn


  reply	other threads:[~2018-08-30 18:50 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
2018-08-30 18:50         ` Chí-Thanh Christopher Nguyễn [this message]
  -- 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=051805c4-1b8a-b887-09b5-106e3604b54f@gentoo.org \
    --to=chithanh@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