From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Ebuild hacking howto
Date: Fri, 25 Feb 2011 10:35:49 -0500 [thread overview]
Message-ID: <4D67CC55.6020203@orlitzky.com> (raw)
In-Reply-To: <loom.20110225T140833-832@post.gmane.org>
On 02/25/2011 08:13 AM, James wrote:
> Hello,
>
> Is the link below the best "howto" guide as to using
> an existing ebuild to hack a new ebuild? JFFNMS has
> been languishing despite repeated requests for a version
> bump; so I'm taking the plunge and going to update it
> on one of my systems.....
>
> http://en.gentoo-wiki.com/wiki/Creating_an_Updated_Ebuild
>
>
> Also, I found this guide:
>
> http://devmanual.gentoo.org/
> and
> man 5 ebuild
>
>
> Any other documents I should reference before
> attempinging to update an ebuild on my own
> person overlay dir?
>
> Comments and ideas are most welcome....
>
This has some good information:
http://overlays.gentoo.org/proj/sunrise/wiki/CodingStandards
and like it says at the bottom, many projects will have their own
development documentation.
Aside from that, help is always (well, when the devs are awake)
available on IRC:
#gentoo-dev-help (what it says)
#gentoo-sunrise (most people here are writing/reviewing ebuilds)
next prev parent reply other threads:[~2011-02-25 16:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 13:13 [gentoo-user] Ebuild hacking howto James
2011-02-25 13:41 ` [gentoo-user] " James
2011-02-25 15:35 ` Michael Orlitzky [this message]
2011-02-26 0:43 ` [gentoo-user] " Mark Shields
2011-02-26 8:28 ` Mick
2011-02-26 14:56 ` Dale
2011-02-26 16:28 ` Mick
2011-02-26 20:16 ` Marc Joliet
2011-02-28 1:43 ` Mark Shields
2011-02-28 1:53 ` Mike Gilbert
2011-02-28 15:45 ` [gentoo-user] " James
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=4D67CC55.6020203@orlitzky.com \
--to=michael@orlitzky.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