Martin Wilck wrote:
[...] Coming back to the original question - I could of course move e.g. multipathd to /usr/sbin now - for TW. But on SLE or Leap, I would run high risk of scripts (from the distro, 3rd party, qa, users, ...)
Obviously don't do that. If you have to backport a package from TW to SLE the old locations have to be used. Can be done with a conditional on %suse_version < 1550 for example.
In this case at least, I find it pretty obvious that simply keeping /sbin is the least error-prone and the least problematic approach, and will automatically do "the right thing" after the usr merge in TW, as well.
Yes. Also multipath-tools is an annoying case. It has the split built in upstream in custom Makefiles already. For that it would be worth a try to get rid of the split upstream. A backport could then move the files where there need to be in the spec file. Anyway, this is how it could look with current sources: https://build.opensuse.org/request/show/898310 cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.com/ SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer HRB 36809 (AG Nürnberg)