From: Mark P. <ms...@de...> - 2004-12-17 13:38:51
|
On Thu, 16 Dec 2004 12:14 pm, Till Kamppeter wrote: > "make install" should not call chkconfig or similar tools to set up the > links for the startup scripts, or it should be easy to turn this off by > a command line setting, as in an RPM or Debian package "make install" is > not run on the machine where the actual installation takes place. > chkconfig is usua;;y called by the postinstall script of the package. > This script is executed when one installs the package and not already > when one build the package. Under hpoj we did this through a user_install and root_install candidates, the Debian package only ever called user_install and manually copied/ setup things like /etc. > For Mark > -------- > > The patch on your home page adds all machine-generated files as logs and > so on to the package. It has more than 50000 (!) lines. The relevant > part are only the 130 lines which you are showing in your e-mail, but in > the e-mail they are destroyed by e-mail-encoding. Probably the biggest > part of your Debian package are these superflous lines. Yes what is up on my homepage is a quick and dirty attempt to get a Debian package going. Certainly not meant to provide the final solution, but at least identify some of the issues and made some suggestions. I'm glad some have been able to been taken upstream. > Your patch comments away the installation of pcardext.so, a C library > for the python programs to access memory cards. So most probably your > Debian package will not be able to read memory cards. Until the $(DESTDIR) support was fixed I was copying pcardext.so and a couple of other python bits manually in the debian/rules part. Thanks for your comments Till. Btw, I'm about to go offline for a month as I relocate to the UK, so I maybe silent for a while. Mark |