On Thu, Apr 21, 2005, Michael van Elst wrote:
On Thu, Apr 21, 2005 at 12:13:38PM +0200, Matthias Kurz wrote:
[...]
Packages in RPM/PKG are only relevant when you do not upgrade
but reinstall the version (with the same options or a superset of
the options) that was once installed.
Maybe it
On Fri, Apr 22, 2005 at 10:27:58AM -0700, Doug Summers wrote:
checking whether the C compiler (/openpkg/bin/cc -O2 -pipe
-I/openpkg/include/pth -I/openpkg/include -I/openpkg/include/pth
-L/openpkg/lib -L/openpkg/lib/pth -L/openpkg/lib) works... no
configure: error: installation or
OpenPKG 2.3.0, Solaris 7. Following RPM's are installed:
autoconf-2.59-2.3.0
automake-1.9.5-2.3.0
binutils-2.15-2.3.0
bison-2.0-2.3.0
flex-2.5.31-2.3.0
fsl-1.6.0-2.3.1
gcc-3.4.3-2.3.0
gpg-pubkey-63c4cb9f-3c591eda
grep-2.5.1a-2.3.1
libiconv-1.9.2-2.3.0
libtool-1.5.14-2.3.0
m4-1.4.2-2.3.0
On Fri, Apr 22, 2005, David M. Fetter wrote:
The noreplace rpmmacros addition works perfectly for us. It solves all
of our problems that we were having with auto-updating and working
configs being overwritten. However, the .rpmmacros existence causes
another side effect on linux systems because
On Fri, Apr 22, 2005 at 08:45:23AM +0200, Matthias Kurz wrote:
On Thu, Apr 21, 2005, Michael van Elst wrote:
On Thu, Apr 21, 2005 at 12:13:38PM +0200, Matthias Kurz wrote:
[...]
Packages in RPM/PKG are only relevant when you do not upgrade
but reinstall the version (with the same options
The noreplace rpmmacros addition works perfectly for us. It solves all
of our problems that we were having with auto-updating and working
configs being overwritten. However, the .rpmmacros existence causes
another side effect on linux systems because it is seen by the OS rpm as
well as openpkg
