Hi David, I can understand the need. I think the best option would be to: a) document your setup b) do what VMWare does: just print a message telling people to run a setup application next, during package installation.
My personal opinion is that there's only two methods of installing software on Linux: a) RPM b) badly For many reasons. You should really avoid installing or creating unpackaged installs. Mike On Mon, 2002-09-23 at 09:47, David Fitch wrote: > On Mon, 2002-09-23 at 09:01, Mike MacCana wrote: > > > On Fri, 2002-09-20 at 20:59, Matthew Hannigan wrote: > > > hmm well won't work in this case, looks like I'll have to > > > provide an install script and pack the lot up as a tarball. > > > Hardly worth making an rpm really. > > > > This is no more effort than making a tarball. Just put the setup script > > as another source in your package. Its nto hard. And its better than the > > tarball system in that: > > yeah but point is doing it like that requires someone to manually > run the setup after the rpm is installed. What I want is the rpm > to automatically do it. So I'll have to make a tarball of the > rpm and an install script, where the install script will simply > consist of "rpm -Uvh *.rpm ; mypostinstallbits". > > Dave. > > > -- > SLUG - Sydney Linux User's Group - http://slug.org.au/ > More Info: http://lists.slug.org.au/listinfo/slug -- ____________________________________________________________________________ Mike MacCana Support Consultant RHCE, MCSE, MCP+I Cybersource: Providing Quality IT Professional Services for 11 Years Specialists in Unix/Linux, TCP/IP and Web Application Development Level 9, 140 Queen St, Melbourne. Ph : 03 9642 5997 Fax: 03 9642 5998 -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
