public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dave Nebinger" <dnebinger@joat.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] no ebuild what to do?
Date: Thu, 29 Sep 2005 13:37:28 -0400	[thread overview]
Message-ID: <003d01c5c51c$76febf90$4501010a@jnetlab.lcl> (raw)
In-Reply-To: <20050929171834.79065.qmail@web31710.mail.mud.yahoo.com>

> I'd like to install dekagen but there are no ebuilds
> for it. I suppose I could just unpack it and follow
> the INSTALL doc but is that the appropriate gentoo
> way?

It's the general unix way of doing things, so sure it fits into gentoo also.
Ebuilds are not really necessary unless you believe a lot of other folks
will be using the same package.

That said, having written some ebuilds lately, I can tell you for the most
part the process is pretty easy.  Start with an ebuild for a package that is
similar to what you're going to install, make the various changes for the
package (the gentoo doc for the ebuilds is your best friend here), and drop
it into your overlay.  If you want to release it, it goes easily into
bugs.gentoo.org.

If you don't want to do the ebuild yourself, and you believe at some point
in the future someone else might get one into portage, you can always use
the ./configure script to install to /usr/local - it would still be
available yet allows for future emerging should it get added.



-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2005-09-29 18:01 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 [this message]
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
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='003d01c5c51c$76febf90$4501010a@jnetlab.lcl' \
    --to=dnebinger@joat.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