On Sun, Mar 30, 2014 at 04:00:28PM +0100, Richard W.M. Jones wrote:
> So first I'll say these are interesting articles, and I encourage
> people to read them.
Thanks!
> I work better when I see some examples of what this would mean in
> practice. Under Fedora.next, how & where would you see the following
> being packaged?
> - libvirt
> Big, with lots and lots of big dependencies, but for virtualization
> it's pretty much the definition of a core, stable API.
Yeah, all of those dependencies present a problem, because some of those are
pretty fast moving. I think conceptually, in the modern world where
virtualization is everwhere, it belongs in the base. (I think certainly both
the server and workstation products will want it, and possibly cloud in some
cases.) The Base WG is trying to define a self-hosting core, though, and
it's possible that it'd be better for this to live outside of that.
> - virt-manager
> An application written in Python, and therefore needing to be "above"
> the stacks layer, I think?
Right, that is more clear.
--
Matthew Miller -- Fedora Project -- <mat...@fedoraproject.org>
"Tepid change for the somewhat better!"
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
