I just ran into what seems to be to be a wierd problem. I built our normal selection of packages on one SuSE Linux Enterprise 9 (SLES9) system which created the tag suse9. I then installed the binary packages on another SLES9 system where the OS is identical.
I had a problem with clamav giving an invalid instruction on the second machine so did an ``openpkg build -z binutils gcc'' to rebuild since the second machine has is a VIA EPIA while the first has an Intel Celeron processor, figuring that the difference in CPU might make a difference. The build process included a rebuild of openpkg itself to the latest CURRENT version (the rest is primarily Release 2.3). After rebuilding openpkg, the tag had changed from suse9 to linux2.6 which naturally broke the generated update script. Why would the tag change since I didn't specify any when originally bootstrapping OpenPKG? Bill -- INTERNET: [EMAIL PROTECTED] Bill Campbell; Celestial Software LLC UUCP: camco!bill PO Box 820; 6641 E. Mercer Way FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676 URL: http://www.celestial.com/ ``Capitalism works primarily because most of the ways that a company can be scum end up being extremely bad for business when there's working competition.'' -rra ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List openpkg-dev@openpkg.org
