in the embedded environment for which we are evaluating RPM for, space is a very
So what we are actually trying to avoid is caching of the packages in the file system
and installing them right away over the network connection. Package numbers will be
between 1-20. I am not sure if this whole scenario would work over the network,
but the question came up if its possible and I try to find out. Not sure if this is enough
information about the scenario / use case we have in mind.
I must admit I did not understand the hint about package manifests.
From: email@example.comSubject: Re: Piping a rpm package into rpm commandDate: Mon, 3 Mar 2008 10:00:21 -0500To: firstname.lastname@example.org
On Mar 3, 2008, at 9:44 AM, Stefan Westmeier wrote:
Hi, just wanted to know if there is any chance that rpm packages can be piped into the rpm command!?
Could be done, but there has to be some demonstrable need.
For starters, a single package on stdin is a rather naive idea. Most rpm
transactions are composed of 100's or 1000's of packages, and
stdin is just not the best input method for concatenated packages themselves.
The issue that needs solving is that *.rpm CLI arguments are open'd
twice, the 2nd time on on a (*notify) callback, in order to permit media to
be changed by installers.
But an open fdno could be cached and used instead. In fact rpm used
to do exactly that until the no. of open fdno's limit was exceeded (and distro's
had to support multiple cd install's).
OTOH, it would not be impossibly hard to pass the paths to packages,
rather than the packages themselves, on stdin. the rpm CLI already supports
package manifests, stdin could be used as an alternative manifest.
73 de Jeff
Received on Tue Mar 4 11:48:22 2008