Fridrich Strba 2014-05-15 11:37:26 +00:00 committed by Git OBS Bridge
parent 907bc863eb
commit f8fbf1ce52
2 changed files with 30 additions and 30 deletions

View File

@ -5,20 +5,20 @@ Thu May 15 11:06:07 UTC 2014 - fstrba@suse.com
* From upstream reasoning:
Some specifications we want to stay compatibility actually
document /var/run, not /run, and we should stay compatible with
that. In order to make sure our D-Bus implementation works on
any system, regardless if running systemd or not, we should
always use /var/run which is the only path mandated by the
D-Bus spec.
Similar, glibc hardcodes the utmp location to /var/run, and
this is exposed in _UTMP_PATH in limits.h, hence let's stay in
sync with this public API, too.
We simply do not support systems where /var/run is not a
symlink -> /run. Hence both are equivalent. Staying compatible
with upstream specifications hence weighs more than cleaning up
superficial appearance.
document /var/run, not /run, and we should stay compatible with
that. In order to make sure our D-Bus implementation works on
any system, regardless if running systemd or not, we should
always use /var/run which is the only path mandated by the
D-Bus spec.
Similar, glibc hardcodes the utmp location to /var/run, and
this is exposed in _UTMP_PATH in limits.h, hence let's stay in
sync with this public API, too.
We simply do not support systems where /var/run is not a
symlink -> /run. Hence both are equivalent. Staying compatible
with upstream specifications hence weighs more than cleaning up
superficial appearance.
-------------------------------------------------------------------
Sat May 3 17:21:00 UTC 2014 - hrvoje.senjan@gmail.com
@ -39,7 +39,7 @@ Sat May 3 17:21:00 UTC 2014 - hrvoje.senjan@gmail.com
instead of the previous 64 (fdo#71297)
- cope with \r\n newlines in regression tests, since on
Windows, dbus-daemon.exe uses text mode (fdo#75863)
-------------------------------------------------------------------
Mon Jan 20 22:08:24 UTC 2014 - hrvoje.senjan@gmail.com

View File

@ -5,20 +5,20 @@ Thu May 15 11:06:07 UTC 2014 - fstrba@suse.com
* From upstream reasoning:
Some specifications we want to stay compatibility actually
document /var/run, not /run, and we should stay compatible with
that. In order to make sure our D-Bus implementation works on
any system, regardless if running systemd or not, we should
always use /var/run which is the only path mandated by the
D-Bus spec.
Similar, glibc hardcodes the utmp location to /var/run, and
this is exposed in _UTMP_PATH in limits.h, hence let's stay in
sync with this public API, too.
We simply do not support systems where /var/run is not a
symlink -> /run. Hence both are equivalent. Staying compatible
with upstream specifications hence weighs more than cleaning up
superficial appearance.
document /var/run, not /run, and we should stay compatible with
that. In order to make sure our D-Bus implementation works on
any system, regardless if running systemd or not, we should
always use /var/run which is the only path mandated by the
D-Bus spec.
Similar, glibc hardcodes the utmp location to /var/run, and
this is exposed in _UTMP_PATH in limits.h, hence let's stay in
sync with this public API, too.
We simply do not support systems where /var/run is not a
symlink -> /run. Hence both are equivalent. Staying compatible
with upstream specifications hence weighs more than cleaning up
superficial appearance.
-------------------------------------------------------------------
Sat May 3 17:21:00 UTC 2014 - hrvoje.senjan@gmail.com
@ -39,7 +39,7 @@ Sat May 3 17:21:00 UTC 2014 - hrvoje.senjan@gmail.com
instead of the previous 64 (fdo#71297)
- cope with \r\n newlines in regression tests, since on
Windows, dbus-daemon.exe uses text mode (fdo#75863)
-------------------------------------------------------------------
Mon Jan 20 22:08:24 UTC 2014 - hrvoje.senjan@gmail.com