Le samedi 30 juillet 2011 à 16:36 +0200, Lennart Poettering a écrit : > On Thu, 28.07.11 09:49, Andreas Jaeger (a...@suse.com) wrote: > > > How are other distros packaging systemd? The systemd 31 release now adds > > devel > > files, so I consider creating a systemd-devel package. > > > > Can we all agree - at least the RPM world - to use the same basic split of > > systemd in subpackages? In that case we could keep a version in git and use > > as > > reference. > > We have a slightly different split on Fedora, but we'd acttually like to > clean this up and merge two of those packages again. > > > > > Right now on openSUSE we have: > > * systemd > > * systemd-gtk > > * systemd-sysvinit > > What is this one for? (We used to have one like this, but we dropped > that when systemd become the only supported init system in Fedora)
systemd-sysvinit is only used to create the various compatibility symlinks for /sbin/init, halt, shutdown, etc.. For openSUSE 12.1, we still plan to have both sysvinit and systemd coexist. > > * systemd-plymouth > > Note that we will soon move the Plymouth unit files into Plymouth proper > and they will then be removed from systemd. And we don't enable plymouth support by default yet, so it is not really an issue. > On Fedora we have two further packages: > > systemd-units: exists mostly for legacy reasons and we hope to fold this > back into systemd soon, if we manage to get the upgrade path right. > > systemd-sysv: contains some compat code which i'd like to get rid of in > F17 or so. > > putting this together we have: > > systemd > systemd-units (will go away) > systemd-sysv (will go away) > systemd-gtk > systemd-devel > > > And I would now introduce > > * systemd-devel for include files, pkg files and .so link > > > > This common usage would make life easier for people developing packages for > > several distributions that require systemd at build time, > > So I am wondering about systemd-sysvinit. Otherwise it looks like we'll > eventually have the same packaging on Suse and Fedora. From what I see in your sysvinit package, it doesn't do exactly the same thing, it is mostly to package the convert script which save the initscripts states before migrating them to systemd units equivalent. -- Frederic Crozat <fcro...@suse.com> SUSE _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
