On 20/10/15 04:23, Khem Raj wrote:
On Oct 16, 2015, at 8:51 AM, Joshua Lock wrote:
There are recipes in the Core metadata that have optional systemd
support but expect the old, separate, libsystemd-foo pkg-config files
(not the newer unified libsystemd).
Add a PACKAGECONFIG option to build s
* Joshua Lock [151019 21:53]:
> On 19/10/15 13:57, Anders Darander wrote:
> >* Joshua Lock [151016 17:52]:
> >>There are recipes in the Core metadata that have optional systemd
> >>support but expect the old, separate, libsystemd-foo pkg-config files
> >>(not the newer unified libsystemd).
> >
> On Oct 16, 2015, at 8:51 AM, Joshua Lock wrote:
>
> There are recipes in the Core metadata that have optional systemd
> support but expect the old, separate, libsystemd-foo pkg-config files
> (not the newer unified libsystemd).
>
> Add a PACKAGECONFIG option to build systemd with the compatib
On 19/10/15 13:57, Anders Darander wrote:
* Joshua Lock [151016 17:52]:
There are recipes in the Core metadata that have optional systemd
support but expect the old, separate, libsystemd-foo pkg-config files
(not the newer unified libsystemd).
Any size impact? Just wondering as you're changi
* Joshua Lock [151016 17:52]:
> There are recipes in the Core metadata that have optional systemd
> support but expect the old, separate, libsystemd-foo pkg-config files
> (not the newer unified libsystemd).
Any size impact? Just wondering as you're changing the default.
(Assuming that it was of
There are recipes in the Core metadata that have optional systemd
support but expect the old, separate, libsystemd-foo pkg-config files
(not the newer unified libsystemd).
Add a PACKAGECONFIG option to build systemd with the compatibility
pc files and default to enabling this option so that we can
