On Sat, Nov 3, 2012 at 5:16 PM, Tom Gundersen wrote:

"As systemd is now the default init system, Arch Linux is receiving minimal testing on sysvinit/initscripts systems. Due to a lack of resources and interest, sysvinit/initscripts-specific bugs may now be closed as WONT FIX.

We therefore strongly encourage all users to migrate to systemd as soon as possible: <link to guide>.

For the time being, sysvinit/initscripts support will remain in the official repositories, unless otherwise stated. As of January 2013, sysvinit/initscripts support may be removed from individual packages without further notice."

Unless there are any objections, I'll put this up soon so I can start closing bugs without feeling bad about it ;-) -t

On Sun, Nov 4, 2012 at 4:51 PM, Andreas Radke wrote:

...

Unless there are any objections, I'll put this up soon so I can start closing bugs without feeling bad about it ;-)

-t

+1

-Andy

Done. -t

Am 07.11.2012 08:59, schrieb Lukas Jirkovsky:

...

As to forcibly removing all the rc scripts by a certain date, I guess we could get back to that later once we see how things pan out? I'd be fine with doing it, but don't see the urgency.

It would be great if maintainers who are going to drop the rc scripts from their package would notify me, so I can keep then in a rc-scripts package as discussed previously (similar to what was done with systemd)

Lukas

Thomas suggested to have a git repo which would contain all those scripts. Everytime a TU or DEV removes a rc script he can commit it there. -- Pierre Schmitz, https://pierre-schmitz.com

On 8 November 2012 16:03, Pierre Schmitz wrote:

Am 07.11.2012 08:59, schrieb Lukas Jirkovsky:

...

It would be great if maintainers who are going to drop the rc scripts from their package would notify me, so I can keep then in a rc-scripts package as discussed previously (similar to what was done with systemd)

Lukas

Thomas suggested to have a git repo which would contain all those scripts. Everytime a TU or DEV removes a rc script he can commit it there.

-- Pierre Schmitz, https://pierre-schmitz.com

That sound like a good idea. +1 from me. Lukas

On Thu, Nov 8, 2012 at 5:54 PM, Lukas Jirkovsky wrote:

On 8 November 2012 16:03, Pierre Schmitz wrote:

...

Am 07.11.2012 08:59, schrieb Lukas Jirkovsky:

...

It would be great if maintainers who are going to drop the rc scripts from their package would notify me, so I can keep then in a rc-scripts package as discussed previously (similar to what was done with systemd)

Lukas

Thomas suggested to have a git repo which would contain all those scripts. Everytime a TU or DEV removes a rc script he can commit it there.

Hello, I've cleaned all packages where I maintain rc scripts. Lukas J. has moved the legacy to a community[1] package[2]. Unless we decide otherwise rc scripts will be dropped when package will be updated / rebuilded. Users who has still not moved to systemd will probably suffer of this. So we can imagine solution to have a smoother transition. By example, patch initscripts to look at 2 places (etc/rc.d and usr/lib/initscripts) allowing a package providing all rc.d to avoid conflict with legacy packages. Cheers, [1] Is community package a good strategy for legagy initscripts? (an AUR package or a git in project.al.org would be better) [2] https://projects.archlinux.org/svntogit/community.git/tree/sysvinit-scripts/... -- Sébastien "Seblu" Luttringer https://www.seblu.net GPG: 0x2072D77A