Re: Switch all packages to /usr?

On 6/8/21 5:34 AM, Martin Wilck wrote:

On Mo, 2021-06-07 at 12:35 -0400, Neal Gompa wrote:

...

On Mon, Jun 7, 2021 at 12:10 PM Martin Wilck wrote:

...

I for one would clean this up when I update one of my package in a way that I know won't go into SLE any more anyway, but no sooner.

But when is that? None of the rest of us peons get to know that.

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, ...) breaking because they expect it in /sbin. I can fix the distro scripts (even that would be some effort to begin with, and pretty error-prone), but I can do hardly anything about the rest. I don't think we'd gain anything if I move the binary to /usr/sbin and create a separate symlink in /sbin. Therefore I believe strongly that multipathd in SLE will remain in /sbin. OTOH, I try to avoid growing too many differences between TW and SLE/Leap spec files, too, and keep conditionals in spec files on a comprehensible level. 

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.

I guess the way it could be done and they way we handle many other similar things is make the change now in tumbleweed and then leave it as is in SLE / Leap and it will automatically be made there in the next major release where it can be properly documented etc. Otherwise in the 6 months leading up to whenever we next branch tumbleweed for the next SLE release all of a sudden people will start to care about these things again and it will all happen at one in a mad rush and or get put off again. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B