2013/1/28 Clinton Stimpson :
> On Monday, January 28, 2013 10:07:04 PM Eric Noulard wrote:
>> 2013/1/28 Clinton Stimpson :
>> > When I try installing a cpack generated .rpm package on another machine,
>> > it
>> > also installs a handful of other dependent packages (including the 32 bit
>> > libc.s
On Monday, January 28, 2013 10:07:04 PM Eric Noulard wrote:
> 2013/1/28 Clinton Stimpson :
> > When I try installing a cpack generated .rpm package on another machine,
> > it
> > also installs a handful of other dependent packages (including the 32 bit
> > libc.so.6 for one of the 32 bit executable
2013/1/28 Clinton Stimpson :
>
> When I try installing a cpack generated .rpm package on another machine, it
> also installs a handful of other dependent packages (including the 32 bit
> libc.so.6 for one of the 32 bit executables among all the 64 bit ones).
>
> But a cpack generated .deb package i
On Monday, January 28, 2013 11:59:46 AM Clinton Stimpson wrote:
> When I try installing a cpack generated .rpm package on another machine, it
> also installs a handful of other dependent packages (including the 32 bit
> libc.so.6 for one of the 32 bit executables among all the 64 bit ones).
>
> Bu
When I try installing a cpack generated .rpm package on another machine, it
also installs a handful of other dependent packages (including the 32 bit
libc.so.6 for one of the 32 bit executables among all the 64 bit ones).
But a cpack generated .deb package isn't that smart. Is there any way to