On Fri, Jun 23, 2017 at 03:56:16PM -0400, Colin Walters wrote: > But one can (and is definitely expected to in many general cases) > to use layered packages. A lot (but not all) of the functionality of dnf > is also possible with rpm-ostree - increasingly so, for example we're > working on supporting "removing" things from the base tree: > https://github.com/projectatomic/rpm-ostree/pull/797 I think we'll want to test _both_ this and ostree updates (and rollbacks), right? > > way to do it. What I'm really kinda looking for is more specific > > details on the level of "here is approximately what you could do to > > reliably put a Workstation ostree system into a state where an update > > for it would be available through the usual mechanism". > We already indeed do these types of things in CentOS CI. Do the results of that get put out to fedmsg? > (Though origin-clients isn't yet in "workstation-ostree" partly due > to this ongoing slow moving debate about whether it's "the same > workstation, just with rpm-ostree" or whether it's something more > different than that where e.g. devel tools are always in a > container, one uses openshift for local server development etc) FWIW, I'm in favor of "more different". Let's make it interesting and stand out. -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
