[arch-dev-public] sysvinit vs. sysvinit-compat
Hi guys, Those packages have conflicts on each other, sysvinit-compat is in base group, so shouldn't sysvinit moved to extra? greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On Fri, Feb 1, 2013 at 1:37 PM, Tobias Powalowski <tobias.powalowski@googlemail.com> wrote:
Hi guys, Those packages have conflicts on each other, sysvinit-compat is in base group, so shouldn't sysvinit moved to extra?
sysvinit is in a split PKGBUILD with sysvinit-tools which is a depends for systemd-sysvcompat. As sysvinit-tools needs to stay in core, so does sysvinit as we can't have split packages in different repo. So sysvinit will need to remain in core unless we decide to remove the initscripts package. In that case sysvinit won't be necessary anymore. Eric
greetings tpowa
-- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On Fri, Feb 1, 2013 at 8:06 PM, Eric Bélanger <snowmaniscool@gmail.com> wrote:
On Fri, Feb 1, 2013 at 1:37 PM, Tobias Powalowski <tobias.powalowski@googlemail.com> wrote:
Hi guys, Those packages have conflicts on each other, sysvinit-compat is in base group, so shouldn't sysvinit moved to extra?
sysvinit is in a split PKGBUILD with sysvinit-tools which is a depends for systemd-sysvcompat. As sysvinit-tools needs to stay in core, so does sysvinit as we can't have split packages in different repo. So sysvinit will need to remain in core unless we decide to remove the initscripts package. In that case sysvinit won't be necessary anymore.
It should be easierr to drop sysvinit-tools after the next util-linux release I think (as various binaries will move there). -t
participants (3)
-
Eric Bélanger
-
Tobias Powalowski
-
Tom Gundersen