public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bob Phan <bob@evil-core.com>
To: Gentoo Dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Is it acceptable to use 'sed' in ebuild scripts?
Date: Tue, 5 Feb 2002 07:41:51 -0500	[thread overview]
Message-ID: <20020205074151.538ab331.bob@evil-core.com> (raw)

Hello, I've just recently created an ebuild for nethack (put it in
app-games/nethack), however, it's build does not use the standard GNU
autoconf/automake system, but rather forces you to manually edit a config.h
file.  Currently, I have just made a patch for X support that is applied when
you "use X".  I would like to add Qt and GNOME optional support, but using
patches, it is very difficult to have one without the other, or the context
will not match (very messy).  I was instead wondering if using 'sed' within
ebuild scripts was accepted practice, or if I should stick a dependancy for
sed at the top of the file.

Thanks for any help.  I plan on writing a few more (hopefully more trivial)
ebuild scripts for any other software I run across.  Also, where should I
submit the ebuild after it's ready?

Thanks again,
Bob

PS. Great distro.  It's the first I have yet to use where I haven't
immediately found something I disliked, on top of its many other
merits.  Good work!

-- 
/*
 * Bob Phan <bob@evil-core.com,rphan@nrgn.com>
 * Computational Chemistry Informatics
 * Neurogen Corporation
 * (203)488-8201 x4645
 *
 * To understand recursion, you must first understand recursion.
 */


             reply	other threads:[~2002-02-05  4:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-05 12:41 Bob Phan [this message]
2002-02-05  7:18 ` [gentoo-dev] Is it acceptable to use 'sed' in ebuild scripts? Einar Karttunen
2002-02-05 16:05   ` Tod M. Neidt

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=20020205074151.538ab331.bob@evil-core.com \
    --to=bob@evil-core.com \
    --cc=gentoo-dev@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