> Not true; there is another option.
>
> One could install the lgtoclnt RPM on your build box, and then use your
> own spec file to scoop up the binaries that legato's RPM dropped on the
> system and create a binary RPM.  You're repacking a binary only package
> so there will be no %prep, no %build, and likely no %install.  I've done
> this type of thing before (not for lgto* RPMs, yet), and it works fine.
> It's not as nice as having the source, but on the positive side, your
> home-grown RPM for the lgtoclnt package can avoid some of the problems
> with the stock EMC RPM (such as never incrementing the release -- I would
> make it match the build #) and not correctly handling upgrades.

 You could even skip the install step and just use rpm2cpio .rpm |cpio -id
 to get at the binaries ...

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER