Skip to content
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions base/debian/cf_defaults
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
use_cvdalloc=true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In case this ends up with unexpected breakage, would it be safer to first make sure cuttlefish-defaults is installed everywhere it should be before it starts introducing behavioral changes?

If cuttlefish-defaults doesn't intentionally introduce a behavioral change, it is less likely to be rolled back, and then the behavioral change of enabling cvdalloc by default would have a smaller rollback than "uninstall the package."

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's necessarily safer, but it's probably better all the same. I thought the change making cuttlefish-defaults a dependency of cuttlefish-common made it out to a release already, but it turns out it hadn't. I think this change in particular can sit on ice for a bit more.

Loading