In article <a2hb0f$e5$[EMAIL PROTECTED]> you wrote:
> I am preparing to make a pkg for postgresql and ran into a couple of mostly
> philosophical problems :)
>
> Basically I need to let the user know that he has to make changes to his OS
> Setup to let postgresql run correctly., ie on Solaris he has to add a
> couple of lines to his /etc/system file, on FreeBSD he would basically have
> to create a new kernel and on linux he has to change some settings manually
> in the /proc interface.
>
> Now, how do I include that into an rpm ? should I create scripts that do
> the changes (I mean I would shoot a packager changing my kernel ...) or
> what would be the correct way /
Hmmm... a very good question. Our team ad-hoc had no answer. Seems like we
have to discuss the possible solutions and select one after thinking about
them in detail. I've already two sultions in mind:
o dispatch in %post according to %{l_target} (the identifier
for the platform) and directly edit the system
(RSE: I think this is not acceptable)
o create a script (say %{l_prefix}/sbin/postgresql-syssetup) which
dispatch in according to %{l_target} and directly edits the system.
Plus output a banner in %post and mention that sys-admin should
%{l_prefix}/sbin/postgresql-syssetup
(RSE: seems like an acceptable solution)
o just output a banner in %post which mentions the steps the
sysadmin should perform manually to setup system.
(RSE: seems also acceptable, but perhaps a little bit nasty)
o ...
More suggestions?
> PS: sorry for my src.rpm posting, will keep to spec files from now on ...
Yes, .spec's and anything from Source: and Patch: which are
not downloadable from the network.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
