From: Greg Yasko <gyasko@cox.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: no ebuild what to do?
Date: Fri, 30 Sep 2005 02:36:30 +0000 (UTC) [thread overview]
Message-ID: <loom.20050930T043331-410@post.gmane.org> (raw)
In-Reply-To: 20050930141919.AF24.NICK@rout.co.nz
Nick Rout <nick <at> rout.co.nz> writes:
>
> Forgive me for saying so, but this ebuild seems a little off to me:
>
Change it to meet the Gentoo standards, if you have the time. I'd like to see
what all you'd change -- it's my first ebuild & I pirated the structure from
bashburn-1.6.ebuild:)
-G.Y.
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-09-30 2:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-29 17:18 [gentoo-user] no ebuild what to do? maxim wexler
2005-09-29 17:30 ` A. Khattri
2005-09-29 17:30 ` Michael Crute
2005-09-29 17:37 ` Dave Nebinger
2005-09-29 18:19 ` Yoandy Rodriguez
2005-09-29 22:05 ` Nick Rout
2005-09-30 2:04 ` [gentoo-user] " Greg Yasko
2005-09-30 2:12 ` Greg Yasko
2005-10-01 20:54 ` maxim wexler
2005-10-02 4:38 ` Nick Rout
2005-09-30 2:27 ` Nick Rout
2005-09-30 2:36 ` Greg Yasko [this message]
2005-09-30 3:59 ` Nick Rout
2005-10-01 17:50 ` maxim wexler
2005-10-01 18:20 ` maxim wexler
2005-10-03 10:53 ` Neil Bothwick
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.20050930T043331-410@post.gmane.org \
--to=gyasko@cox.net \
--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