summaryrefslogtreecommitdiff
path: root/doc/todo/merge_request:_changes_to_Reboot.hs/comment_3_6460a7f85249bd8b9a83f2e145a25d62._comment
blob: 3d842ac35bde9b98d15e3d3aa4cef103688d1639 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
[[!comment format=mdwn
 username="joey"
 subject="""comment 3"""
 date="2016-06-14T04:04:50Z"
 content="""
It might also be worth making the Sbuild properties know 
whether overlays are desired. Then they could make sure to set up the
config file with the needed lines, even if the wrong kernel is running.

I assume schroot fails to work in that configuration, so the properties
for it would fail and then the user would notice they need to add a
property to get a new enough kernel version..

It could be specified with another parameter to the Sbuild properties.
Or, you could add a pure Info property `useOverlays` and have the
Sbuild properties check if the Info has that set. This would also
let Schroot.overlaysInTmpfs require useOverlays and auto-enable them.

Most of the implementation of that:

	useOverlays :: Property (HasInfo + UnixLike)
	useOverlays = pureInfoProperty "use schroot overlays" (InfoVal UseOverlays)
	
	data UseOverlays = UseOverlays

	useOverlays :: Propellor Bool
	useOverlays = isJust . fromInfoVal
		<$> (askInfo :: Propellor (InfoVal UseOverlays))
"""]]