Re: SUMMARY: rpm -e

2004-03-17 Thread Matthias Kurz
On Tue, Mar 16, 2004, Mike's List wrote:

 
 Thanks to: Bill Campbell, Steffen Weinreich, and Thomas Lotterer for
 the quick replies.  The below command works.
 
 In addition, you can rebuild the package and do an rpm -U --force to
 do the new installation.  I decided to remove/reinstall to be safe.

Maybe this was best suited for your case. Generally an update is better
than a remove/reinstall, i think, because the update retains modified
config files in most cases.


   (mk)

-- 
Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47
   Im prämotorischen Cortex kann jeder ein Held sein. (bdw) 
__
The OpenPKG Projectwww.openpkg.org
User Communication List  [EMAIL PROTECTED]


Re: Rebuild Apache with options

2004-03-17 Thread Matthias Kurz
On Wed, Mar 17, 2004, Michael van Elst wrote:

 On Wed, Mar 17, 2004 at 07:18:38AM +0100, Michael van Elst wrote:
 
  rpm --rebuild --define 'with_php yes' --define 'with_php_mysql yes' apache
 
 That should have been:  'with_mod_php yes' and 'with_mod_php_mysql yes'.
 

And it would probably better to use openpkg build, wouldn't it ?

openpkg build -Dapache::with_mod_php=yes -Dapache::with_mod_php_mysql=yes apache | sh

One can also create a file $HOME/.openpkg/build and put those options in
it (one option per line).


   (mk)

BTW: There are no manual pages except openpkg.1 under CURRENT. And the
 manual pages for rpm are under .../libexec. But i think this is
 work in progress...

-- 
Matthias Kurz; Fuldastr. 3; D-28199 Bremen; VOICE +49 421 53 600 47
   Im prämotorischen Cortex kann jeder ein Held sein. (bdw) 
__
The OpenPKG Projectwww.openpkg.org
User Communication List  [EMAIL PROTECTED]


Re: Rebuild Apache with options

2004-03-17 Thread Ralf S. Engelschall
On Wed, Mar 17, 2004, Mike's List wrote:

rpm --rebuild --define 'with_php yes' --define 'with_php_mysql yes' apache
  
   That should have been:  'with_mod_php yes' and 'with_mod_php_mysql yes'.
  
 
  And it would probably better to use openpkg build, wouldn't it ?
 
  openpkg build -Dapache::with_mod_php=yes -Dapache::with_mod_php_mysql=yes apache | 
  sh
 
  One can also create a file $HOME/.openpkg/build and put those options in
  it (one option per line).

 # openpkg build -Dapache::with_mod_php=yes -Dapache::with_mod_php_mysql=yes \
 apache | sh
 openpkg:ERROR: No such command build found in command path
 openpkg:ERROR: (/openpkg/libexec/openpkg).
 openpkg:ERROR: Set $OPENPKG_TOOLS_CMDPATH appropriately.
 openpkg:ERROR: Run /openpkg/bin/openpkg --help for list of valid commands.

 I don't see this build feature with openpkg.  I saw rpmbuild when doing
 openpkg --help.  Is this what you're referring to as build?

openpkg build is provided by the openpkg-tool addon package.

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

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


Re: SUMMARY: rpm -e

2004-03-17 Thread Michael Schloh von Bennewitz
On Wed, Mar 17, 2004, Matthias Kurz wrote:
 Yes, i thought that modified config files are saved as *.rpmsave by rpm
 when a package is removed, but i was not sure. Most of the time it is
 still unessesary work to move them back after reinstallation. And it is
 error prone because you may forget it and you are not informed when the
 format of the config file changed... 

Careful, since OpenPKG 1.3 you are indeed warned by the rc program when using it with 
packages
that have such .rpmsave or .rpmnew files in their config directories. Try
putting a blank 'thisthing.rpmsaved' file under /prefix/etc/apache/ and then
run 'rc apache stop' or some other 'rc apache ...' command.

There is however no warning from RPM itself after a sucessful package
upgrade.

-- 
[EMAIL PROTECTED]
Development Team, Operations Northern Europe
Cable  Wireless Telecommunications Services


pgp0.pgp
Description: PGP signature