[omniORB] omniORB 4.0.3 and omniORBpy 2.3 available

[Thomas Lockhart]

> michelle:~ # rpm --showrc |grep "vendor"
> - -14: _build_vendor      %{_host_vendor}
> - -14: _host_vendor       suse
> - -14: _target_platform   %{_target_cpu}-%{_vendor}-%{_target_os}
> - -14: _target_vendor     %{_host_vendor}
> - -14: _vendor    suse

Given the results of SuSE and Mandrake, it looks like _target_vendor 
might be the best choice (on Mandrake, _vendor is "MandrakeSoft" rather 
than "mandrake"). Can someone check these same values for a recent RH 
installation?

>>Failed during packaging (usually due to missing or ignored files):
>>   rpm -bb --short-circuit omniORB.spec
>>   rpm -bs --short-circuit omniORB.spec
> These do the same as rpm -ba (dunno why).

I recall that behavior also, but am pretty sure I've seen differently 
recently. The packaging checks may also run during the installation 
phase, so perhaps it isn't a big deal since you want to go back through 
with a "-ba" anyway.

> It defaults to i386. Maybe that can cause the problems?

You probably want to just use what the vendor suggests. Or override it 
on the command line when you build the rpms. That way we can integrate 
the spec file for more distros.

> You also need (for some reason) to do the following:
> chmod a+x $RPM_BUILD_ROOT/etc/init.d/omniNames

OK. Will adjust the spec file.

>>># install SuSE rc start script
>>>mkdir -p $RPM_BUILD_ROOT/usr/sbin
>>>ln -sf ../../etc/init.d/omniNames $RPM_BUILD_ROOT/usr/sbin/rcomniNames
>>I *think* this one should go into the post-installation section for boot
>>scripts. I've had trouble getting soft links to stay "soft" when
>>packaging if I just use the %files section to solve it.
> I found that the link stays symbolic after I installed my bootscripts rpm.
> I checked through suse's hotplug src rpm spec file for clues as to how to
> insert the rcomniNames link. 

Hmm. Some other distros put the files into the init.d directory (like 
SuSE) but do not bother with a soft link into /usr/sbin. Does SuSE also 
have the rcX.d directories and chkconfig to adjust what runs when?

Mandrake and RH use /sbin/service to access the boot scripts, as in

   service omniNames start|stop|restart

>>If things are failing here, please send the text of the RPM output. Not
>>sure what the problem with the spec file might be, except perhaps SuSE
>>looks for something a bit different.
> Will do. I am busy with a run that reincludes them and does not specify the
> architecture (like the first time I did a successful run).

Great. Send the spec file and we can do a couple more iterations of 
merging to get everything happy.

Duncan, is there anything in this discussion which gives you concern 
about accepting these changes back into the omniORB distro?

                     - Tom