From: Victor <victor@enise.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: How to contribute ebuilds?
Date: Mon, 25 Apr 2016 00:20:41 +0300 [thread overview]
Message-ID: <20160425002041.0205f6da@probook> (raw)
In-Reply-To: <loom.20160424T185859-563@post.gmane.org>
On Sun, 24 Apr 2016 17:11:54 +0000 (UTC)
James <wireless@tampabay.rr.com> wrote:
> Victor <victor <at> enise.org> writes:
>
>
> > I have a couple of ebuilds for some software not in main tree,
> > mainly emacs and python modules.
> > What is the preferred way to contribute them without becoming a
> > Gentoo Developer?
>
> I think the preferred method (it takes time to go down the gentoo-dev
> or gentoo-proxy-maintainer pathways) is to setup a github acccount
> and post your body of work there because github makes it easy for
> folks to collaborate with you and your work.
>
> [...]
>
> > Should I post them to bugzilla or maybe send to `python' and `emacs'
> > overlays (if so, how?), or `sunrise' overlay? Or create my own
> > overlay?
>
> Yes, that way, we get immediate access to the ebuilds to test them
> out and give you feedback. Put up some details, related to these
> packages, either in bgo or a github/blog, particularly if they are
> part of a theme you are pursuing.
Thanks.
> Who knows, maybe you'll also want to bring turbogears2 to gentoo?
> That would be very, bery cool! Turbogears1 use to be part of the
> packages available. Turbogears2 is very cool [1].
I've never used turbogears, I'll take a note :)
prev parent reply other threads:[~2016-04-24 21:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-24 11:42 [gentoo-user] How to contribute ebuilds? Victor
2016-04-24 11:50 ` Sam Jorna
2016-04-24 11:54 ` Sam Jorna
2016-04-24 21:11 ` Victor
2016-04-24 17:11 ` [gentoo-user] " James
2016-04-24 21:20 ` Victor [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=20160425002041.0205f6da@probook \
--to=victor@enise.org \
--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