On Mon, Jun 19, 2017, at 07:25 PM, Matthew Miller wrote:
On Mon, Jun 19, 2017 at 03:22:31PM -0400, Colin Walters wrote:
> But bigger picture than that, having a split `/home` makes less sense using
> rpm-ostree, because the primary original rationale for introducing that split
> was to make upgrades easier by reinstalling but preserving `/home`. With
> rpm-ostree upgrades should be much more reliable and easier.
I guess the cost here is that it makes it harder to decide that you
wanted non-Atomic workstation after all. But as long as we're just
changing the default, I don't have a strong opinion.
You mean if you wanted to reinstall and keep /home? Yeah,
but the flip side is with a "not all space allocated" installation
default, one can carve out space from the VG for a new install and
copy /home. I don't think Anaconda has any specific UI for that,
but you could even do it post install, just keep the existing
partition and mount /home.
I'd say the current target audience is to some degree expected
to have sufficient expertise for these types of things. At least I am
certainly going to be investing in making sure that we smooth
over sufficient issues that going back will hit fewer people.
But a good example of something that people will hit is
https://github.com/projectatomic/rpm-ostree/issues/233
and I can certainly imagine that being a blocker. OTOH
what the Chrome RPM is doing is horrific and it has enough
hooks in /usr anyways that it'd just make more sense there.
(Or really, as a flatpak but that's a whole other story)