Remind me how dropping this in Tumbleweed affects Leap, in even one single way?  You do understand that Leap is based on SLE, and as long as SLE supports SysVInit scripts, that's going to remain true for Leap.   Just because a change gets made in Factory/Tumbleweed, that doesn't mean it automatically makes it into Leap.


On June 18, 2024 12:23:47 PM CDT, "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2024-06-18 19:09, Shawn W Dunn wrote:
On 6/18/24 05:33, Carlos E. R. wrote:
On 2024-06-18 14:04, Thorsten Kukuk via openSUSE Factory wrote:
On Tue, Jun 18, 2024 at 12:55 PM Carlos E. R.
<robin.listas@telefonica.net> wrote:

On 2024-06-18 09:54, Thorsten Kukuk via openSUSE Factory wrote:

/sbin/service is used by rc* symlinks by us.  Is there anything else
calling /sbin/service?

/etc/vmware, maybe.

A config file should not call a binary...

Oops. Typo.

/etc/init.d/vmware

And the vmware scripts in our open-vm-tools package will not use
/sbin/service, as the network script they try to execute with it does
not exist...

I see /etc/init.d/rc3.d/K50vmware and @K50vmware-USBArbitrator,
@S50vmware and @S50vmware-USBArbitrator, and in level 5, 2.

Whatever that is, it doesn't seem to come from openSUSE.

No, they come from vmware player, a proprietary package.

...


I absolutely wouldn't advocate for holding up progress in openSUSE, due to the needs of some third party proprietary package.   VMWare or not.

Leap is compatible with SLES. I do not consider dropping support for important proprietary packages a good business selling point.