From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: qwinff: an excellent qt gui front-end for ffmpeg
Date: Tue, 11 Nov 2014 14:32:03 +0000 (UTC) [thread overview]
Message-ID: <loom.20141111T142854-702@post.gmane.org> (raw)
In-Reply-To: 20141111084814.7c8aa972@digimed.co.uk
Neil Bothwick <neil <at> digimed.co.uk> writes:
> On Tue, 11 Nov 2014 03:04:46 +0000 (UTC), James wrote:
> > The more folks putting software into ebuilds and making them avaialbe,
> > either github or overlay (sunshine) the better off we all are.
> Or post them to bgo where they will hopefully get picked up by a dev or a
> layman overlay.
Since it is "QT" maybe. Here is mesos, I fixed: bgo 510912:: walt action ->
(from dev who put lxqt-0.8.0 together>
"When you'll have ebuild less or more prepared, you can ask for review on
sunrise irc channel: #gentoo-sunrise. Also you can ask for commit access to
the sunrise overlay: https://wiki.gentoo.org/wiki/Project:Sunrise/How_to_commit
If you do not like sunrise overlay, I still recommend you ask there for
review, then I can help you with proxy-maintainment:
https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers "
From what I can discern, a group of forward-thinking devs actually want
the user community to "step-up" and start building the easier ebuilds
our distro needs to be inclusive with the thousands of packages that
other distros have.
POWer_tools maintainer :: dev_da_walt ?
It's kind of fun, hacking at ebuilds :: the devs have just got to
put in a bit more work to give users the tools, examples and support
we need to "get er done", imho.
hth,
James
prev parent reply other threads:[~2014-11-11 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 2:14 [gentoo-user] qwinff: an excellent qt gui front-end for ffmpeg walt
2014-11-11 3:04 ` [gentoo-user] " James
2014-11-11 8:48 ` Neil Bothwick
2014-11-11 14:32 ` James [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=loom.20141111T142854-702@post.gmane.org \
--to=wireless@tampabay.rr.com \
--cc=gentoo-user@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