From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Ebuild hacking howto
Date: Mon, 28 Feb 2011 15:45:46 +0000 (UTC) [thread overview]
Message-ID: <loom.20110228T164332-711@post.gmane.org> (raw)
In-Reply-To: AANLkTinUsjX0yWJwziJPfoUBh3z7gqv6sGTebgKtOXMG@mail.gmail.com
Mark Shields <laebshade <at> gmail.com> writes:
> Saw that you linked to the "creating an updated ebuild" from gentoo-wiki, so
what I say may overlay quite a bit, but hear me out:
> Attachment (jffnms-0.8.5.ebuild): application/octet-stream, 2207 bytes
Mark,
I appreciate your answer very much. I'm looking at this now as we speak.
I'll follow up tomorrow on the results of my efforts, using your
suggestions.
thanks very much,
James
prev parent reply other threads:[~2011-02-28 15:47 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 ` [gentoo-user] " Michael Orlitzky
2011-02-26 0:43 ` 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 ` 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.20110228T164332-711@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