On Wed, Jan 22, 2014 at 12:46:33PM +0100, Mark Trompell wrote: > On Wed, Jan 22, 2014 at 12:18 PM, Michael K. Johnson <[email protected]> > wrote: > > The rpm:rpm component is the actual encapsulated RPM package > > of RPM that Conary hands off to RPM to install. > > Ok, I think I start to understand the whole thing a bit better now. > But would conary verify still work? what would a conary q foo --lsl show?
Yes, conary verify will still work. Conary records all the files in the RPM, including things like marking configuration files. It just adds a flag to every file that comes from an RPM as a capsule file so that Conary doesn't try to process it separately; it doesn't store it separately in the repository, nor does it lay it down separately on the system. (The exception, if my memory serves after several years, is configuration files; I believe the content of configuration files is replicated into Conary directly in order to enhance configuration file handling.) _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
