Quote:
Originally Posted by unSpawn
Location alteration is not a valid reason in my book and neither would be a "repack". Why complicate things unnecessary when you can use relocation instead?
|
It's unfortunately the way we decided to CM certain software packages, and in order to maintain consistency with the install process that we have, I am following the same methodology. We could have CM'd the package as part of the OS install, but we decided to package all of the base build and runtime environment packages separately.
Quote:
Originally Posted by unSpawn
I didn't see you try a 'rpm -i --nodeps'?
|
I felt that would be cheating and working around a problem. Of course if it is an unresolvable "feature" then I will resort to that.
Quote:
Originally Posted by unSpawn
|
Quote:
Originally Posted by kbp
When you created the package did you define the Requires or let rpmbuild automatically resolve them?
|
I let rpmbuild automatically resolve the dependencies, it appears that post #4 from the centos topic says to turn off the auto resolve and manually add the requires for those libraries. What is it about the auto-resolver that would prevent the install from finding the libraries? Is there a "feature" in rpm that could be fixed, or is it more involved than that? Auto resolving is always much easier than manually setting dependencies.