core-admin/linux/system-config/Makefile

all:
	true

install:
	mkdir -p $(DESTDIR)/etc/xen/scripts
	cp vif-route-qubes $(DESTDIR)/etc/xen/scripts
	cp block-snapshot $(DESTDIR)/etc/xen/scripts
	ln -s block-snapshot $(DESTDIR)/etc/xen/scripts/block-origin
	install -d $(DESTDIR)/etc/xdg/autostart
	install -m 0644 qubes-guid.desktop $(DESTDIR)/etc/xdg/autostart/
	install -m 0644 qrexec-policy-agent.desktop $(DESTDIR)/etc/xdg/autostart/
	install -m 0644 -D tmpfiles-qubes.conf $(DESTDIR)/usr/lib/tmpfiles.d/qubes.conf
	install -d $(DESTDIR)/etc/dbus-1/system.d
	install -m 0644 dbus-org.qubesos.PolicyAgent.conf  \
		$(DESTDIR)/etc/dbus-1/system.d/org.qubesos.PolicyAgent.conf
rpm+makefile: move build/install code to Makefile files This makes build "scripts" not tied to Fedora-specific files. Especially ease porting to other platforms. 2013-06-15 23:14:54 +02:00			`all:`
			`true`

			`install:`
			`mkdir -p $(DESTDIR)/etc/xen/scripts`
			`cp vif-route-qubes $(DESTDIR)/etc/xen/scripts`
			`cp block-snapshot $(DESTDIR)/etc/xen/scripts`
			`ln -s block-snapshot $(DESTDIR)/etc/xen/scripts/block-origin`
			`install -d $(DESTDIR)/etc/xdg/autostart`
			`install -m 0644 qubes-guid.desktop $(DESTDIR)/etc/xdg/autostart/`
qubespolicy: run GUI code inside user session and expose it as dbus object This way it will work independently from where qrexec-policy tool will be called (in most cases - from a system service, as root). This is also very similar architecture to what we'll need when moving to GUI domain - there GUI part will also be separated from policy evaluation logic. QubesOS/qubes-issues#910 2017-04-06 15:39:31 +02:00			`install -m 0644 qrexec-policy-agent.desktop $(DESTDIR)/etc/xdg/autostart/`
Use tmpfile.d to create /var/run subdirs This way it will be done much earlier, so qubes-db can be started before qubes-core.service - which will solve startup dependency loop problem. 2015-02-02 04:48:42 +01:00			`install -m 0644 -D tmpfiles-qubes.conf $(DESTDIR)/usr/lib/tmpfiles.d/qubes.conf`
qubespolicy: run GUI code inside user session and expose it as dbus object This way it will work independently from where qrexec-policy tool will be called (in most cases - from a system service, as root). This is also very similar architecture to what we'll need when moving to GUI domain - there GUI part will also be separated from policy evaluation logic. QubesOS/qubes-issues#910 2017-04-06 15:39:31 +02:00			`install -d $(DESTDIR)/etc/dbus-1/system.d`
			`install -m 0644 dbus-org.qubesos.PolicyAgent.conf \`
			`$(DESTDIR)/etc/dbus-1/system.d/org.qubesos.PolicyAgent.conf`