What I want to do is to have a policy in squeeze that supports running wheezy in a basic configuration. If a daemon that is in wheezy gets a new feature and breaks then I'm not too bothered (I am not aiming for full compatibility). But I want to have the basics work for everyone (which includes /run) and have most daemons work.
Now for unstable I can have the new selinux-policy-default which works with /run depend on the new libselinux1 and everything will be fine. For a transition from squeeze to wheezy I guess I could patch selinux-policy- default to support /run but not have it depend on a new libselinux1 so that an upgrade from squeeze to wheezy will get the new libselinux1 and then start working. This seems to imply that any package which breaks selinux-policy-default should also break libselinux1 to force an upgrade. Also it means that the version of selinux-policy-default should be upgraded in the next squeeze update to not be broken. Does this seem correct? If so would it be achievable with the release process? -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
