Yeah, I guessing forcing you into using src rpms is a bit Big Brother-ish, but then again, this is Redhat we're talking about.:)
However, I'm only typically finding dependency problems with my src compiled libraries. It's a huge mess trying to use something like up2date when a key library isnt registered with rpm. I think that part of using a package manager is playing nicely with it. That's sorta the price of the convenience.
If, for the "skeletal" libraries, you force yourself to use src rpms, then you shouldnt have too much issue with the userland applications that are hard to find in rpm. If there's no rpm for the library in question, then your chances of having dependency issues with that library are next to nil in the first place.
Basically, if you use rpms where they are available, then you shouldnt have dependency problems.
Aren't the src rpms designed to handle this specific problem?
Instead of downloading the src in tar format, you install the src rpm, and build the src rpm into a binary rpm. Then you not only have a custom compiled binary, but also a custom binary rpm to pass around your machines and a proper dependencies library.
Slashdot Mirror
Yeah, I guessing forcing you into using src rpms is a bit Big Brother-ish, but then again, this is Redhat we're talking about. :)
However, I'm only typically finding dependency problems with my src compiled libraries. It's a huge mess trying to use something like up2date when a key library isnt registered with rpm. I think that part of using a package manager is playing nicely with it. That's sorta the price of the convenience.
If, for the "skeletal" libraries, you force yourself to use src rpms, then you shouldnt have too much issue with the userland applications that are hard to find in rpm. If there's no rpm for the library in question, then your chances of having dependency issues with that library are next to nil in the first place.
Basically, if you use rpms where they are available, then you shouldnt have dependency problems.
Aren't the src rpms designed to handle this specific problem? Instead of downloading the src in tar format, you install the src rpm, and build the src rpm into a binary rpm. Then you not only have a custom compiled binary, but also a custom binary rpm to pass around your machines and a proper dependencies library.