On Wed, Mar 19, 2014 at 03:56:47PM -0400, Chris Lumens wrote: > Well it could be a wrapper distributed with anaconda. I guess I see > anaconda's role as taking an input specification (kickstart, though that > kickstart may take the form of UI interaction these days) and producing > as output an installation to some destination. If you want to further > process that destination (in this case, by packing it up into a tarball) > then that should be done by some other program. > We've got other anaconda wrappers laying around (liveinst being the most > visible example) so it's not that weird of a suggestion. *nod* okay, yeah. That'd be just fine. > > Actually the firewalld case is already fixed. So I guess it's just > > authconfig left. > Where are you seeing that firewalld is fixed? This: <https://bugzilla.redhat.com/show_bug.cgi?id=1004976>. Is it all lies? :) > First, like I said, it's a pretty specific set of tasks that applies to > one specific function - making images for docker to use. I don't like > the idea of adding something so very specific into code that's trying to > handle a variety of installations. Well, Docker is the container format du jour, but what goes into the container is broader than that. That said, some of the examples I gave are terrible and probably should be dealt with in other ways. For example, when nspawn is used to start the container, it takes care of the device stuff. However, the idea of making sure the images are written with the expectation that they'll be copied and reused is going to be generally useful. > Second, this feels like something that's going to grow and shrink over > time. We're going to be constantly chasing it. Or, we can put someone > who knows what's needed in charge of maintaining it. Yes, I think this is completely true. -- Matthew Miller -- Fedora Project -- <mattdm@xxxxxxxxxxxxxxxxx> _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
