1 |
What Ive seen in other ebuilds is a file with the default options |
2 |
that just gets sent to the "interactive setup script via stin. (ie no need |
3 |
for expect) |
4 |
|
5 |
take a look at /usr/portage/app-games/freecraft/freecraft-1.18.ebuild |
6 |
and /usr/portage/app-games/freecraft/files/setup.input |
7 |
|
8 |
cat ${FILESDIR}/setup.input | ./setup || die "setup failed" |
9 |
|
10 |
nothing offical, just my observations |
11 |
|
12 |
|
13 |
-AMiel |
14 |
|
15 |
|
16 |
|
17 |
|
18 |
On Tue, 10 Jun 2003, MAL wrote: |
19 |
|
20 |
I'm writing an ebuild for ZoneMinder, and I have a few problems/queries.. |
21 |
|
22 |
The program is a bunch of php and a few cgi apps. After configuring, |
23 |
the package asks you to run a perl script which interactively asks you |
24 |
for initial configuration, then updates the .php files with this info. |
25 |
'make install' then installs the .php files into your document root, |
26 |
(and the cgi into your cgi-bin dir). |
27 |
|
28 |
Now, I don't want to break the non-interactivity of portage, but I can't |
29 |
just leave an 'einfo' message to the user after install, asking them to |
30 |
run the perl script, because this must be done before install. |
31 |
|
32 |
So, do I either: |
33 |
|
34 |
* Use expect to answer the perl script's questions with some sensible |
35 |
defaults, then leave a message to the user on how to change these |
36 |
defaults after install, (in which case, should I add expect to the |
37 |
DEPEND line?) |
38 |
|
39 |
* Re-package the software entirely, (there is a compiled part and a |
40 |
non-compiled php part.. maybe separate the php part out). I'm kinda |
41 |
loathed to do this, as it seems like unnecessary maintenance. |
42 |
|
43 |
* Modify the perl script to automatically set certain defaults. |
44 |
|
45 |
|
46 |
Additionally, what do I do about the location of apache, and the |
47 |
user/group to set the php files as? :) |
48 |
I noticed the recent eclass submission, but I'm assuming I can't use |
49 |
that just yet, so /home/httpd/htdocs and apache:apache ? |
50 |
|
51 |
Cheers, |
52 |
MAL |
53 |
|
54 |
|
55 |
-- |
56 |
gentoo-dev@g.o mailing list |
57 |
|
58 |
|
59 |
-- |
60 |
gentoo-dev@g.o mailing list |