On 24/07/13 10:33 AM, Alexandre Rostovtsev wrote: > On Wed, 2013-07-24 at 16:17 +0200, Ulrich Mueller wrote: >>>>>>> On Wed, 24 Jul 2013, Michał Górny wrote: >> >>> Pacho requested that to be able to warn users in GNOME packages that >>> do not work anymore without systemd. >> >> Why is the host where the package is built required to run systemd? >> Wouldn't a warning at runtime better suit the purpose? > > The purpose of systemd_is_booted() is to provide helpful postinst > messages to users depending on whether or not they are running systemd, > and for the vast majority of users, the machine where the package is > built is the machine where the package will be run. > > Runtime warnings would require non-trivial patching of the packages in > question, so it's not a realistic alternative. > > Those who have separate build hosts are probably sufficiently > technically proficient to understand if the message does not apply to > their case. > >
So it is sufficient to add e.g. ewarn_systemd_is_not_booted() (possibly with a better name) to discourage inappropriate use cases?
signature.asc
Description: OpenPGP digital signature
