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

[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 crontab

No.

> - etc...
> (almost like a Windows installer ;) )

Most certainly not. :)

> What is the correct way: just install the basic elements and let the
> user do the rest of the setting up, or do as much as possible?

Let the user do it, you can put some post-install instructions into a
README.SLACKWARE file, there are numerous examples in the repo.

-- 
Erik Hanson
http://slackbuilds.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20091016/40255af4/attachment.asc>