Currently work is being made to offer alternatives to sysvinit in Slackware such as OpenRC and Runit, as they are the most complete init replacement systems. Work has been slow in progress, but there are solid efforts to bring offerings around over at LinuxQuestions. We have been met with resistance, but so far, we are still somewhat active in the efforts.

To: james4591@???; dng@???
Subject: RE: [Dng] Slackware systemd creepin in maybe?
From: yvesjv@???
Date: Thu, 21 May 2015 05:28:46 +1000

Hi James,
Thanks for the info.

Keeping Slack stable is the reason why some have picked this excellent distro instead of a bsd during the mass migration away from the systemd/Debian debacle.
Sure hope the same fiasco that occurred with systemd/Debian does not happen with Slack in future.

IMHO, that would be very destructive to Slackware :-(


Thanks again and keep slacking.




----- Original Message -----
From: "James Powell" <james4591@???>
To:"Anto" <aryanto@???>, <yvesjv@???>, <dng@???>
Cc:
Sent:Tue, 19 May 2015 14:18:40 -0700
Subject:RE: [Dng] Slackware systemd creepin in maybe?



Hey guys, let me clarify the Slackware position on systemd.


Patrick has no intent on enforcing the usage of systemd upon Slackware and it's users unless it becomes an unavoidable issue. So far, this has not been the case in the slightest, and we doubt it will be. Slackware intends to keep the bsd-stylized sysvinit implementation.


Packages do have some systemd files for systemd systems, but because all packages in Slackware try to stay as vanilla as possible to "./configure && make && make install" methodology. You are free to remove them after-the-fact, or modify the Slackbuild scripts
to remove them during the package construction stages.


There is a systemd experimental repackage of Slackware called Dlackware by a package developer named bartgymnast, but while the repack is specific to systemd, it is unsupported, unofficial, and still considered unstable in build.


I hope this clarifies this.


Sent from my Windows Phone


From:
Anto
Sent:
‎5/‎19/‎2015 12:14 PM
To:
yvesjv@???;
dng@???
Subject:
Re: [Dng] Slackware systemd creepin in maybe?






On 19/05/15 20:31, yvesjv@??? wrote:

>

> Hi Anto,

>

> From your posts it appears that you are doing a lot of work cleaning

> up these packages.

>

> Apologies if I've missed a previous post as I think it would be

> extremely helpful to all interested if you documented your invaluable

> work on a wiki of sorts?

>

> Perhaps more could assist with the cleanups :-)

>

>

> Thanks

>


Yes, it has been quite a lot of work for me, especially due to the lack

of my skills in the programming and Debian packaging as I am just an

ordinary user. So what I have been doing is basically trial and error :)


Change something, re-compile, revert back when fails, again and again

until the packages get successfully compiled. But that is not the end of

it. The installation of the packages that have been successfully

compiled are not always smooth. I broke my install several times. But I

didn't spend time to troubleshoot, again due to the lack of my skills.

After taking some logs and notes on something which I thought might be

related to the changes that I made. I put back the disk image which I

always take before any installation, then start all over again :)


So I think that is quite embarrassing, especially for Devuan (for me, I

don't really care) if that kind of process would be documented some

where on Devuan site :)


I have leant a lot by reading the commits on Devuan gitlab, especially

the ones with the title related to "removing systemd" like
https://git.devuan.org/packages-base/dbus/commit/2ebb243f3fa51790d93e7f21a11dca324df6b0fd,

https://git.devuan.org/packages-base/network-manager/commit/665eb3cb32e9ca3f4294f783375e4118d9b78427


and many others.


Cheers,


Anto


_______________________________________________

Dng mailing list

Dng@???
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng