public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexey Mishustin <shumkar@shumkar.ru>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: media-sound/mhwaveedit
Date: Tue, 10 Dec 2019 15:44:35 +0300	[thread overview]
Message-ID: <CAGWFrguF83p8r+AHknEd5ANTiyJ1HAQDkHECB6WZo+VoWigyKA@mail.gmail.com> (raw)
In-Reply-To: <88f11edaa36fed2c79c68c227e4690445f965e6b.camel@gentoo.org>

вт, 10 дек. 2019 г. в 15:13, David Seifert <soap@gentoo.org>:
>
> On Tue, 2019-12-10 at 13:39 +0300, Alexey Mishustin wrote:
> > вт, 10 дек. 2019 г. в 03:47, David Seifert <soap@gentoo.org>:
> > > # David Seifert <soap@gentoo.org> (2019-12-10)
> > > # Build broken for over 3 years, GTK 2, quasi-abandoned upstream.
> > > # Bug #490574, #699914. Removal in 30 days.
> > > media-sound/mhwaveedit
> >
> > I'm sorry to hear that.
> >
> > I consider it the best, fastest and simplest audio editor for Linux
> > and use it for years on several systems. Last time I've built it on a
> > new system in this November without any problem (x86_64, USE="alsa
> > nls
> > sndfile").
> >
> > The last release at [1] is dated 25 Aug 2018.
> >
> > I see a one-line patch in the bug #490574 that has not been neither
> > used nor rejected: [2].
> >
> > But I don't feel myself capable of helping maintain it. Just sorry.
> >
> > --
> > [1] https://github.com/magnush/mhwaveedit/releases
> > [2] https://490574.bugs.gentoo.org/attachment.cgi?id=437158
> >
>
> Due to popular demand, I fixed all bugs and modernized the ebuild.
> Unmasked again.

Many thanks, David!

I am looking at your commit and learning (again) how to work with ebuilds.

-- 
Regards,
Alex


      reply	other threads:[~2019-12-10 12:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  0:46 [gentoo-dev] Last rites: media-sound/mhwaveedit David Seifert
2019-12-10 10:39 ` Alexey Mishustin
2019-12-10 12:13   ` David Seifert
2019-12-10 12:44     ` Alexey Mishustin [this message]

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=CAGWFrguF83p8r+AHknEd5ANTiyJ1HAQDkHECB6WZo+VoWigyKA@mail.gmail.com \
    --to=shumkar@shumkar.ru \
    --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