Re: [Slackbuilds-users] How far should doinst.sh go?

2009-10-16 Thread Phillip Warner
uilds-users] How far should doinst.sh go? > To: "SlackBuilds.org Users List" > Date: Friday, October 16, 2009, 7:09 AM > On Fri, Oct 16, 2009 at 9:11 AM, Erik > Hanson > wrote: > > On Oct 16, 2009, at  9:03 AM, Niels Horn wrote: > > > >> Should the doi

Re: [Slackbuilds-users] How far should doinst.sh go?

2009-10-16 Thread Niels Horn
On Fri, Oct 16, 2009 at 9:11 AM, Erik Hanson wrote: > On Oct 16, 2009, at  9:03 AM, Niels Horn wrote: > >> Should the doinst.sh just do the basic, like updating the menu, check >> /etc/(program) config files etc.? > > Yes. > >> Or, should it also: >> - set up a MySQL database if the software needs

Re: [Slackbuilds-users] How far should doinst.sh go?

2009-10-16 Thread Erik Hanson
On Oct 16, 2009, at 9:03 AM, Niels Horn wrote: > Should the doinst.sh just do the basic, like updating the menu, check > /etc/(program) config files etc.? Yes. > Or, should it also: > - set up a MySQL database if the software needs it No. > - create needed users & groups No. > - change cron

[Slackbuilds-users] How far should doinst.sh go?

2009-10-16 Thread Niels Horn
Should the doinst.sh just do the basic, like updating the menu, check /etc/(program) config files etc.? Or, should it also: - set up a MySQL database if the software needs it - create needed users & groups - change crontab - etc... (almost like a Windows installer ;) ) I know this could get trick