public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Amiel Martin <martina3@cc.wwu.edu>
To: MAL <mal@komcept.com>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuild question
Date: Thu, 12 Jun 2003 04:34:52 -0700 (PDT)	[thread overview]
Message-ID: <Pine.GSO.4.21.0306120429440.11231-100000@titan.cc.wwu.edu> (raw)
In-Reply-To: <3EE5EA76.7090805@komcept.com>

What Ive seen in other ebuilds is a file with the default options
that just gets sent to the "interactive setup script via stin. (ie no need
for expect)

take a look at /usr/portage/app-games/freecraft/freecraft-1.18.ebuild
and /usr/portage/app-games/freecraft/files/setup.input

cat ${FILESDIR}/setup.input | ./setup || die "setup failed"

nothing offical, just my observations


-AMiel




On Tue, 10 Jun 2003, MAL wrote:

I'm writing an ebuild for ZoneMinder, and I have a few problems/queries..

The program is a bunch of php and a few cgi apps.  After configuring, 
the package asks you to run a perl script which interactively asks you 
for initial configuration, then updates the .php files with this info. 
'make install' then installs the .php files into your document root, 
(and the cgi into your cgi-bin dir).

Now, I don't want to break the non-interactivity of portage, but I can't 
just leave an 'einfo' message to the user after install, asking them to 
run the perl script, because this must be done before install.

So, do I either:

* Use expect to answer the perl script's questions with some sensible 
defaults, then leave a message to the user on how to change these 
defaults after install, (in which case, should I add expect to the 
DEPEND line?)

* Re-package the software entirely, (there is a compiled part and a 
non-compiled php part.. maybe separate the php part out).  I'm kinda 
loathed to do this, as it seems like unnecessary maintenance.

* Modify the perl script to automatically set certain defaults.


Additionally, what do I do about the location of apache, and the 
user/group to set the php files as? :)
I noticed the recent eclass submission, but I'm assuming I can't use 
that just yet, so /home/httpd/htdocs and apache:apache ?

Cheers,
MAL


--
gentoo-dev@gentoo.org mailing list


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-06-12 11:34 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-10 14:25 [gentoo-dev] ebuild question MAL
2003-06-10 15:40 ` [gentoo-dev] A nice idea to improve portage MooktaKiNG
2003-06-10 16:07   ` Matthew Kennedy
2003-06-10 18:05   ` John Robinson
2003-06-10 20:20     ` Philippe Lafoucrière
2003-06-11  3:18       ` Luke Graham
2003-06-11  5:10         ` Bill Kenworthy
2003-06-10 21:56     ` MooktaKiNG
2003-06-10 21:42       ` Zach Forrest
2003-06-10 23:26         ` Kumba
2003-06-11 11:52   ` [gentoo-dev] Readme files for portage (was: A nice idea to improve portage) Svyatogor
2003-06-11 10:37     ` MooktaKiNG
2003-06-11 10:10       ` Michael Cummings
2003-06-11 10:44         ` Paul de Vrieze
2003-06-11 13:24         ` [gentoo-dev] " D. Tuinstra
2003-06-11 15:47           ` oford
2003-06-11 17:06         ` [gentoo-dev] " MooktaKiNG
2003-06-12 11:34 ` Amiel Martin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-03  3:40 [gentoo-dev] ebuild question pepone pepone
2005-03-03  3:47 ` Jeremy Hanmer
2005-03-03 10:26   ` Aaron Walker
2005-03-03 20:23     ` Jeremy Hanmer
2005-03-04  0:42       ` Aaron Walker
2003-09-19 14:57 Philippe Lafoucrière
2003-09-19 15:03 ` Georgi Georgiev
2003-09-19 15:12   ` Philippe Lafoucrière
2003-09-19 15:26     ` Georgi Georgiev
2003-09-19 15:05 ` Thomas de Grenier de Latour
2003-09-19 15:15   ` Philippe Lafoucrière
2003-05-30 15:17 William Hubbs
2003-05-30 15:27 ` Grant Goodyear
2003-05-31  3:00   ` Georgi Georgiev
2003-05-30 11:15 MAL
2003-05-30 11:29 ` Alastair Tse
2003-05-30 14:22   ` MAL
2003-05-30 14:33     ` Alastair Tse
2003-05-30 14:40       ` Todd Berman
2003-05-30 14:55         ` Jon Portnoy
2003-05-30 15:08           ` MAL
2003-05-30 14:39     ` Seemant Kulleen
2003-05-30 15:09       ` Seemant Kulleen
2002-11-26 21:27 Per Wigren
2002-11-26 21:23 ` Dan Armak
2002-11-27  0:03   ` Per Wigren
2002-07-26 14:54 John Matthews
2002-04-18  6:13 Avi Schwartz
2002-04-18  6:59 ` George Shapovalov
2002-04-18  7:15 ` Tod M Neidt
2002-04-17  5:21 Richard Jackson
2002-04-17  5:02 ` Jared H. Hudson
2002-04-17  6:05   ` Richard Jackson
2002-04-17  5:21     ` Jared H. Hudson
2002-02-07  3:44 Edward Muller
2002-02-07  4:43 ` Tod M Neidt
2001-08-05 15:50 Craig Joly
2001-08-05 17:07 ` Daniel Robbins

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=Pine.GSO.4.21.0306120429440.11231-100000@titan.cc.wwu.edu \
    --to=martina3@cc.wwu.edu \
    --cc=gentoo-dev@gentoo.org \
    --cc=mal@komcept.com \
    /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