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