Re: Updating rpm should preserve /opkg/etc/rc.d/rc.server

[Ralf S. Engelschall]

On Fri, Oct 15, 2004, Alexander Belck wrote:

 Two questions

 1) specificaly for apache I need the action graceful.
Particulary I would prefer the way other distros handle apache using
apachectl, that in some cases make extra check to avoid killing apache
at all when reloading with a new miss-configuret apache.conf

But at least could be the graceful action added to the standart rc.apache ?

It is already in OpenPKG CURRENT and will show up in OpenPKG 2.2's
apache package. If you there do a reload a graceful restart is
performed.

 2) My lake of knowlege.
How should I use rc.conf ?
I'm not used with that kind of startup, I guess its similar to debian ??

All I found is that all the rc.xxx files from OpenPKG have a %config
section that could change the way a server starts.
Should I repead the configuration settings I whant to change from
rc.xxx in rc.conf with my setting ?

Just place the name=value settings into your rc.conf file
in order to override the ones in the rc.xxx files' %config sections.

   Ralf S. Engelschall
   [EMAIL PROTECTED]
   www.engelschall.com

__
The OpenPKG Projectwww.openpkg.org
User Communication List  [EMAIL PROTECTED]

Re: SpamAssassin final

[Ralf S. Engelschall]

On Fri, Oct 15, 2004, Alexander Belck wrote:

 To prepare my waries :-)) How do I upgrade a production instalation of OpenPKG
 from ver 2.1 to 2.2.
 [...]
 How should I proceed to get the new 2.2 release with all the same build option
 running ?

The same way between 2.0 and 2.1: you upgrade the bootstrap package
openpkg and then all other packages. My usual upgrade procedure is:

$ w3m http://cvs.openpkg.org/openpkg-re/releasenotes.txt
$ prefix/bin/openpkg rpm --rebuild \
  ftp://ftp.openpkg.org/release/N.M/SRC/openpkg-N.M.0-N.M.0.src.rpm
$ prefix/bin/openpkg rpm -Uvh \
  prefix/RPM/PKG/openpkg-N.M.0-N.M.0.*.rpm
$ prefix/bin/openpkg build -Ua upgrade.sh
$ vi upgrade.sh
$ sh upgrade.sh

Using openpkg build preserves your old build options plus/minus the
ones which have changed names (if any). So, although the above works
95% of time without problems and fully automatic, because of slight
differences in available options between releases, the above reading of
the release notes and manual adjustment of the upgrade.sh procedure in
practice is strongly advised. In release notes you will find what was
changed and this has to be reflected usually with a few manually added
--with or --without options in upgrade.sh

 Is it possible to have it at the same /opkg root without an spare Host with
 same underlaying OS (and same hardware??) to build the new pakages ?

I'm not sure whether I understand you correctly. But if /opkg is
your production environment you usually cannot build a set of new
packages for /opkg with it without changing this OpenPKG instance during
building. The reason is that you have to install dependency packages
during building. But you can create a chroot(2) environment and create a
building-only /opkg there.

 Temporarly, is it possible to instruct `openpkg build package`
 to get the lates package from CURRENT Release ?

I think you at least have to specify the path to the CURRENT
00INDEX.rdf.bz2 file manually unless your openpkg bootstrap package is
a CURRENT one.
   Ralf S. Engelschall
   [EMAIL PROTECTED]
   www.engelschall.com

__
The OpenPKG Projectwww.openpkg.org
User Communication List  [EMAIL PROTECTED]