> I hope you mean FreeBSD 4.10, but anyway: Nope, 4.0. That is the whole reason I've migrated to OpenPKG, I'm not all that interested in bring the box down unecessarily, the ports no longer work, but I want a package manager for keeping the packages up to date. 1.3 worked with zero problems.
[snip] > I remember we recently did some portability hacking for the curl > application embedded in the bootstrap. Please try the latest 2.0 [1] > bootstrap and if that doesn't help use the latest CURRENT [2] bootstrap. This would be then what is causing openpkg 1.9 bootstrap to fail? It would seem then that the 1.9 bootstrap would need an upgrade....as I don't have any odd configurations on my system that would have made my failure a special case. > Because you're upgrading from 1.x you have to tweak the spec > to get accepted by the old rpm. Follow the second option of > "upgrade procedure with intermediate step" as described in > http://cvs.openpkg.org/openpkg-re/upgrade.txt What you need is > probably something like a 1.9.3 package which you can create by > installing the source RPM of 2.0.3 and editing the openpkg.spec in > $PREFIX/RPM/SRC/openpkg. Remove the "Class:" header and the %track > section and append the string " [CORE]" to the "Description:" header. > That's the whole difference between 2.0.0 and 1.9.0 anyway. The same > works with CURRENT, too. The 1.9.x number is arbitrary by the way, be > creative. I'll try that tonight when I get home from work. I do have on remaining question before that though. From what you are saying, I can go directly to CURRENT from 1.3 as long as I modify the bootstrap package, correct? After I get the modified bootstrap installed, I am then going to want to install the standard bootstrap, correct? Thanks, Frank ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
