On Jun 19, 2007, at 4:30 PM, Anders F Björklund wrote:
Jeff Johnson wrote:
w00t!
Yes with the necessary va_end patch.
Wondered why my RPM installation suddently stopped working...
Turned out that I updated the outstanding ports and didn't
really browse through entire list. So it updated popt, but
rpm was still compiled with the old internal popt version.
This causes spectacular failures like not finding "rpmq":
$ rpm -qa
rpm: -qa: Invalid argument
Downgrading to popt 1.10_4 again fixed it, will try to
figure out how to make the two co-exist... (rpm/popt)
Do I want to use the internal version, or the external ?
I'd say the path forward is going to be external popt separate from rpm.
For rpm-4.4.9, which still uses popt exec with helpers, popt internal
might be needed/useful, because a popt change can/will cause rpm
break spectacularly, as you have seen.
But we can likely get rpm-4.5 stabilized into macports with less effort
than trying to support two popt's.
The changes in rpm-4.5 are largely structural rearrangements,
like paths for helper executables and scripts, not coding changes.
73 de Jeff
______________________________________________________________________
POPT Library http://rpm5.org
Developer Communication List [email protected]
