Re: archive-installer backend

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 07, 2011 at 06:44:14AM -0400, Martin Sivak wrote:
> does this take into account that we have support for adding additional repositories?
> 
> I was thinking about the backend changes needed to support installing from multiple tarballs (software bundles) and one issue we have to solve is merging rpm metadata (or at least creating them at the end of the installation) so the system has proper information about everything.

I'm definitely not thinking of merging RPM metadata here.  I think that
should be done only by installing packages.  So the only way that makes
sense to me is to be able to lay down a base archive and then use RPM
to install packages on top of the base archive, and I'd think that would
be an edge case to be handled by post-install scripts.  (Otherwise, we
would have to layer backends and ask (I presume) the yuminstall back end
to handle this case.)  This seems like more complexity than it's worth.

My multiple tarball use case was that the additional archives layered on
top of the base archive do not contain packaged software.  The most
obvious case to my mind is config files.

(I expect to post code for more concrete discussion early next week, BTW.)

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux