On Wed 29-05-19 19:59:48, Theodore Ts'o wrote: > On Wed, May 29, 2019 at 02:06:03PM +0200, Lukas Czerner wrote: > > What I am going to do is to split the systemd service into a separate > > package and I'd like to come to some agreement about the name of the > > package so that we can have the same name across distributions (at least > > Fedora/Debian/Suse). > > Hmm.... what keeping the service as part of the e2fsprogs package, but > then not enabling out of the box. That is, require that user run: > > systemctl enable e2scrub_all.timer > > in order to actually get the feature? (They can also disable it using > "systemctl disable e2scrub_all.timer".) > > As far as the cron job is concerned, we could just leave the crontab > entry commented out by default, and require that the user go in and > edit the /etc/cron.d/e2scrub_all file if they want to enable it. Not > packaging it also seems fine; Debian's support for non-systemd > configurations is at best marginal at this point, and while I'm not a > fan of systemd, I'm also a realist... > > What do folks think? Yeah, my plan is to just not package cron bits at all since openSUSE / SLES support only systemd init anyway these days (and in fact our distro people want to deprecate cron in favor of systemd). I guess I'll split off the scrub bits into a separate sub-package (likely e2fsprogs will suggest installation of this sub-package) and the service will be disabled by default. Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR
