[Slackbuilds-users] postgresql again

[Donald Allen]

On Thu, Apr 15, 2010 at 4:03 AM, Tim Dickson <dickson.tim at googlemail.com> wrote:
> just a thought..
>
> It should be easy enough to just echo instructions using doinst.sh
> That way the end user/installer gets to know how to get things working,
> without the package interfering and doing it for them.
> Either that, or (or as well) include the instructions in an rc. file as
> comments, in the same way that the mysql package already does.

And (as I mentioned in my original post) in the README.SBo, together
with the instructions for how to initialize the database. I agree with
Robby that this isn't quite a "bug" -- it's more a documentation
issue. And despite what you've said above, if it turns out to be
inconvenient or undesirable to have the package check for the presence
of the postgres group and user at install time, anyone installing
postgresql is going to have to consult the README.SBo to know how to
edit rc.local/rc.local_shutdown get the server running/stopped and the
database initialized. So having the information about the needed group
and user there seems like the natural place to put it. I'd be happy
with just that. If the package can do the check at install time, so
much the better.

/Don

>
> Tim
>
> On 15/04/2010 03:22, Robby Workman wrote:
>
> On Wed, 14 Apr 2010 12:03:30 -0400
> Donald Allen <donaldcallen at gmail.com> wrote:
>
>
>
> When you run the postgresql.SlackBuild, you get reminded that you need
> to create a postgres group and user and you are given the commands to
> do so. You comply, the postgres package builds, you install it, and
> then get it running following the instructions in README.SBo.
>
> Some time later, you use the resulting package to try to install
> postgresql on another system. It installs, but when you attempt to get
> it running, you can't, because you need to create the postgres group
> and user, which you find out when you attempt to do
>
> su postgres -c "initdb -D /var/lib/pgsql/data"
>
> Except the error you get doesn't tell you how to fix the problem. So
> maybe you remember enough from when you originally built the package
> to dig through the postgresql.SlackBuild and figure it out.
>
> My point is this: the reminders to create the group and user should
> not occur at build time, they should occur at install time (or maybe
> both, if they are really needed at build time). At the very least, the
> README.SBo ought to tell you that the group- and user-creation is
> needed and how to do it. It seems to be assuming that this has already
> been done, which it may not be, if you are installing a package that
> you created on a different system six months ago.
>
> This issue is similar in nature to the issue I had with the gnucash
> package: the package is not self-contained and should be.
>
>
> This one is a WONTFIX, if only because I don't see it as a bug.
>
> That's not to say that I don't see your point -- I do -- but
> there's not any obvious way that we can do this better without
> adding some badness.  By "badness," I mean: we are not going
> to have postinstall scripts create users and/or groups on the
> system.
>
> In essence, this is one of those things that's going to have to
> be documented by the system admin in a local ChangeLog or some
> such and then consulted when doing new installs.
>
> -RW
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>
>
>