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@g.o mailing list


--
gentoo-dev@g.o mailing list