On Mon, Dec 17, 2012 at 09:39:19PM -0400, Fred White wrote:
a script and performs non-interactive installation (using expect).
are application specific RPMs and are currently not available in our
rhn/spacewalk channels. These RPMs needs to be installed in a specific
order and some of them also needs to be installed with nodeps (rpm -i
--nodeps), since there are missing dependencies, and there are vendor
instructions to do so.
A "super rpm" is the wrong tool for the job, here. You _could_ do it, but
you really shouldn't. The same goes for those vendor RPMs, which sound
Issue 1) What are general Fedora packaging guidelines around creating
an RPM? I'm looking to understand what are the caveats
(non-recommendations) to this approach.
"Don't do it." You're pounding in nails with a Cuisinart.
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁ <mattdm(a)fedoraproject.org>