> Although we've still a few important TODO points left
> before we can make OpenPKG 2.0 (see "FIXME" entries in
> http://cvs.openpkg.org/getfile?f=openpkg-re/news.txt), we now have to
> start fixing all CORE, BASE and PLUS packages in preparation for the
> OpenPKG 2.0 release engineering phase which will start in November.
In checking this out, I found:
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
- Platform Identification:
We finally cleaned up the whole platform identification in RPM.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Is this why I can't install packages built with OpenPKG 1.3.1 using OpenPKG RPM 4.2.1
(as I reported in some previous
emails)? e.g.,
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
> rpm -Uvh openpkg-20031006-20031006.sparc64-solaris2.9-ups.rpm, and got:
Preparing... ########################################### [100%]
package openpkg-20031006-20031006 is intended for a solaris2.9 operating system
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
and
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
rpm -Uvh openpkg-20031006-20031006.ix86-linux2.4-upr.rpm, and got:
Preparing... ########################################### [100%]
package openpkg-20031006-20031006 is intended for a linux2.4 operating system
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
If so, this seems a steep price to pay for upgrading...
Dennis
______________________________________________________________________
The OpenPKG Project www.openpkg.org
Developer Communication List [EMAIL PROTECTED]
