RPM package - dependency checks
My question is about dependency checks for the RPM package.
Using a third-party install generation tool, I created an .RPM installation package for my application.
There are several dependencies that are required to be present on user’s Linux OS for my application to run properly.
Specifically, “make”, and several “.so” libraries, like libgcc.so,libc.so, etc.
Not all of our users may have required dependencies installed prior to running my package installer.
This third-party installer tool that I used, generates RPM package, but does not include dependency checks.
As members of the Red Hat community, could you please comment on how a custom .RPM package without dependency checks may be received by users?
Is it acceptable enough to deliver .RPM for a custom application that does not check dependencies?
Or is it uncommon enough to ‘anger’ Linux users?
Last edited by sashadolstar; 10-19-2012 at 07:00 PM.