What is more, but off topic, is that, as anyone know, most commercial rpm
package (when and if are distributed with rpm ), well, are a little scary in
quality, at minimum
rpm -q --scripts TIVsm-AP
postinstall scriptlet (using /bin/sh):
#!/bin/bash
..
...
for f in libgpfs.so libdmapi.so libha_gs_r.so libct_cu.so
do
if [ -f /usr/lib/$f ]
then
if [[ $DEBUG_INSTALL == "1" ]]; then echo "File /usr/lib/$f
found...";fi
else
if [[ $DEBUG_INSTALL == "1" ]]; then echo "File /usr/lib/$f not
found... copy it!";fi
cp $CLIENTDIR/api/bin/$f /usr/lib <-- HARGHHHHHH
fi
done
....
# remove buildDate
rm -f $CLIENTDIR/api/bin/.buildDate <-- HARGHHHHHHHHHHHH
rm -f $CLIENTDIR/lang/.buildDate <-- HARGHHHHHHHHHHHH
#######
rpm -V TIVsm-API
missing /opt/tivoli/tsm/client/api/bin/.buildDate
missing /opt/tivoli/tsm/client/lang/.buildDate
On Wed, Jun 25, 2008 at 6:41 PM, Tim Mooney <[EMAIL PROTECTED]> wrote:
> In regard to: Re: rpm3 package still exist, Jason Corley said (at
> 12:35pm...:
>
> On Wed, Jun 25, 2008 at 12:06 PM, Tim Mooney <[EMAIL PROTECTED]> wrote:
>>
>> If you try sign an RPM built with 3.0.x with a 4.X.Y version of RPM, the
>>> RPM becomes corrupted.
>>>
>>> Would this be something that's easy to fix -- make RPM 5.1.x capable of
>>> signing both modern and ancient RPMs? It sure would make a lot of
>>> sysadmins lives easier, as they wouldn't have to keep an old copy of RPM
>>> around just to sign packages they get from vendors.
>>>
>>
>> Having asked this question once or twice over the last few years I'll
>> save Jeff the hassle of telling you that it's an insoluble problem.
>> So short answer is if it ain't happened by now, it ain't gonna happen.
>> Jason
>>
>
> Thanks Jason. I pretty much figured that was the case, but hope springs
> eternal, as they say. ;-)
>
> Tim
> --
> Tim Mooney [EMAIL PROTECTED]
> Information Technology Services (701) 231-1076 (Voice)
> Room 242-J6, IACC Building (701) 231-8541 (Fax)
> North Dakota State University, Fargo, ND 58105-5164
> ______________________________________________________________________
> RPM Package Manager http://rpm5.org
> Developer Communication List rpm-devel@rpm5.org
>
