Hi all,

Finally I could get online. It's not easy here in Bandung, Indonesia. At
the hotel net access is very expensive, but even if you buy it it doesn't
work (not joking). We finally got to the only 'free' WiFi hotspot in the
city, but the sign saying 'no hidden charges' should made me vary from the
start. Actually you have to deposit a million local credits (about $100)
to get online, and even after that it's only web access (no ssh, pop3,
smtp, etc.).

So I can't log in anywhere, and I can only reply to mail through webmail
(so I have to be quick, only while being here).

> I have corrected some typos, and now the install procedure works (at
> least on my mandrake 10.1). By install procedure, I mean:
> cvs checkout
> configure
> make install.
> Note that for this to work, you need to tell the configure script
> whether you want it to create stuff for you, by using the
> --with-create-database[=yes|no]
> --with-create-odbc-data-source[=yes|no]
> --with-init-database[=yes|no]
> --with-configure-apache[=yes|no]
> command line options. If one of these options is omitted, "no" is
> assumed; if the [=yes|no] part is omitted, that means "yes".

yes, this is all correct

>
> However. The pre- and post- install stuff has been dispersed among the
> various modules, and they are done when 'make install' is executed. Some
> of this is just search-and-replace, but some other things need to be
> done again by the debian package installer.

some stuff, but quite little. basically debian-related.

>
> I have replaced the call to postInstallScheduler.sh by createDatabase.sh
> and createOdbcDataSource.sh, but this is probably not enough. For
> example, PEAR packages need to installed, apache configured, etc.

they are installed when the tools are installed. the tools/pear directory
is also autoconf-style, and it is all called from the main Makefile and
make tools_setup (a whole configure / make / make install cycle is done
there). thus the pear packages are installed even before LS files get
compiled.

>
> It is also possible that we could just put postInstallScheduler.sh (and
> postInstallGLiveSupport.sh?) back, after removing the search-and-replace
> stuff.

there's nothing to be done for gLiveSupport after the normal install.
ponstInstallScheduler is needed to do some finalization for the debian
install itself.

but I made all this stuff, and committed it to the CVS on Tuesday /
Wednesday.

the version that was wroking for me is on the debian demo system, at
/home/maroy/src/dist


>
> I am going to bed now and will continue tomorrow; just thought I'd write
> this down in case anybody wants to continue where I left off.

good to know the progress..


Akos

------------------------------------------
Posted to Phorum via PhorumMail

> I don't understand. I thought the debian package installer just copies
> files and sets up resources and config files. Does it also run 'make

depends on what do you mean by the installer?

at package creation time, it runs make install. all is installed in
/opt/livesupport (then moved, etc.) and then all the installed files are
put into the package. at this time, pear stuff is also installed under
/opt/livesupport/lib , and they are copied with all the other files into
the package itself...

but you're right, the installer at install time does run the
bin/createDatabase.sh script, and thus installs the database tables with
that (as opposed to on make install)

> install'? Because the database etc. are set up during 'make install'.
> Also, how does it know if it needs to set up the database (initial
> install) or not (upgrade)?

read the debian documentation for that, but it acually knows.

> The tools/pear install script is probably just plain broken, and needs
> to be fixed, see bug #1361.

works for me, see /home/maroy/dist/livesupport on the debian demo system
if you don't believe so..

but I have to go offline now..


Akos

------------------------------------------
Posted to Phorum via PhorumMail

> The tools/pear install script is probably just plain broken, and needs
> to be fixed, see bug #1361.

Never mind, this was caused by a stray file in my PATH.

------------------------------------------
Posted to Phorum via PhorumMail