dbus with tests

dbus with tests

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 541 bytes --]

In the process of updating dbus, tests (in my opinion) are mandatory.

While compiling dbus with tests, dbus and dbus-glib are needed. To
compile dbus-glib, dbus is needed (obviously). The only solution (to
compile dbus with tests) that i found is to create a new recipe named
dbus-tests where to compile dbus with --enable-tests
--enable-embedded-tests, skip write to sysroot (noexec) and just package
dbus-tests.

1. Do you guys know a better solution for this?
2. What would be a good path to use for installing tests?


ag

[-- Attachment #2: Type: text/html, Size: 797 bytes --]

Re: dbus with tests

[Saul Wold]

On 08/14/2012 02:11 PM, Andrei Gherzan wrote:
> In the process of updating dbus, tests (in my opinion) are mandatory.
>
> While compiling dbus with tests, dbus and dbus-glib are needed. To
> compile dbus-glib, dbus is needed (obviously). The only solution (to
> compile dbus with tests) that i found is to create a new recipe named
> dbus-tests where to compile dbus with --enable-tests
> --enable-embedded-tests, skip write to sysroot (noexec) and just package
> dbus-tests.
>
> 1. Do you guys know a better solution for this?

We have started to think/chat about this, there was another patch on the 
list recently that Mark Hatle and I talked about tests.

I think having the tests enabled with DISTRO_FEATURE would allow for the 
flexibility of enabling then without always incurring the cost /overhead 
of longer compile times.

Can you incorporate the changes to the core recipe with out having to 
add a new dbus-tests recipe if you use DISTRO_FEATURE?


> 2. What would be a good path to use for installing tests?
Same here, disucssion started.I would like to see tests go into 
${datadir}/${BPN} (/usr/share/${BPN}.  /opt was discussed, but I think 
we want to leave that clean and empty.


Sau!


>
>
> ag
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Re: dbus with tests

[Koen Kooi]

Op 14 aug. 2012, om 13:11 heeft Andrei Gherzan <andrei@gherzan.ro> het volgende geschreven:

> In the process of updating dbus, tests (in my opinion) are mandatory.
> 
> While compiling dbus with tests, dbus and dbus-glib are needed. To compile dbus-glib, dbus is needed (obviously). The only solution (to compile dbus with tests) that i found is to create a new recipe named dbus-tests where to compile dbus with --enable-tests --enable-embedded-tests, skip write to sysroot (noexec) and just package dbus-tests.
> 
> 1. Do you guys know a better solution for this?

It's actually the only solution that would work :)

> 2. What would be a good path to use for installing tests?

$bindir or $libexecdir IMO

Re: dbus with tests

[Koen Kooi]

Op 14 aug. 2012, om 13:57 heeft Saul Wold <sgw@linux.intel.com> het volgende geschreven:

> On 08/14/2012 02:11 PM, Andrei Gherzan wrote:
>> In the process of updating dbus, tests (in my opinion) are mandatory.
>> 
>> While compiling dbus with tests, dbus and dbus-glib are needed. To
>> compile dbus-glib, dbus is needed (obviously). The only solution (to
>> compile dbus with tests) that i found is to create a new recipe named
>> dbus-tests where to compile dbus with --enable-tests
>> --enable-embedded-tests, skip write to sysroot (noexec) and just package
>> dbus-tests.
>> 
>> 1. Do you guys know a better solution for this?
> 
> We have started to think/chat about this, there was another patch on the list recently that Mark Hatle and I talked about tests.
> 
> I think having the tests enabled with DISTRO_FEATURE would allow for the flexibility of enabling then without always incurring the cost /overhead of longer compile times.
> 
> Can you incorporate the changes to the core recipe with out having to add a new dbus-tests recipe if you use DISTRO_FEATURE?
> 
> 
>> 2. What would be a good path to use for installing tests?
> Same here, disucssion started.I would like to see tests go into ${datadir}/${BPN} (/usr/share/${BPN}

$datadir is not for executables, but for data

> .  /opt was discussed, but I think we want to leave that clean and empty.

/opt is for 3rd party binary-only stuff, it should *never* show up in a system package.

Re: dbus with tests

[Andrei Gherzan]

[-- Attachment #1: Type: text/plain, Size: 1676 bytes --]

On Tue, Aug 14, 2012 at 3:50 PM, Koen Kooi <koen@dominion.thruhere.net>wrote:

>
> Op 14 aug. 2012, om 13:57 heeft Saul Wold <sgw@linux.intel.com> het
> volgende geschreven:
>
> > On 08/14/2012 02:11 PM, Andrei Gherzan wrote:
> >> In the process of updating dbus, tests (in my opinion) are mandatory.
> >>
> >> While compiling dbus with tests, dbus and dbus-glib are needed. To
> >> compile dbus-glib, dbus is needed (obviously). The only solution (to
> >> compile dbus with tests) that i found is to create a new recipe named
> >> dbus-tests where to compile dbus with --enable-tests
> >> --enable-embedded-tests, skip write to sysroot (noexec) and just package
> >> dbus-tests.
> >>
> >> 1. Do you guys know a better solution for this?
> >
> > We have started to think/chat about this, there was another patch on the
> list recently that Mark Hatle and I talked about tests.
> >
> > I think having the tests enabled with DISTRO_FEATURE would allow for the
> flexibility of enabling then without always incurring the cost /overhead of
> longer compile times.
> >
> > Can you incorporate the changes to the core recipe with out having to
> add a new dbus-tests recipe if you use DISTRO_FEATURE?
> >
>

As Koen as said in another mail i don't think there is another option than
creating another recipe and we could add RDEPENDS to dbus if DISTRO_FEATURE
contains dbus-tests.


> >
> >> 2. What would be a good path to use for installing tests?
> > Same here, disucssion started.I would like to see tests go into
> ${datadir}/${BPN} (/usr/share/${BPN}
>
> $datadir is not for executables, but for data
>
>
Binaries and scripts?

ag

[-- Attachment #2: Type: text/html, Size: 2364 bytes --]

Re: dbus with tests

[Saul Wold]

On 08/14/2012 03:49 PM, Koen Kooi wrote:
>
> Op 14 aug. 2012, om 13:11 heeft Andrei Gherzan <andrei@gherzan.ro> het volgende geschreven:
>
>> In the process of updating dbus, tests (in my opinion) are mandatory.
>>
>> While compiling dbus with tests, dbus and dbus-glib are needed. To compile dbus-glib, dbus is needed (obviously). The only solution (to compile dbus with tests) that i found is to create a new recipe named dbus-tests where to compile dbus with --enable-tests --enable-embedded-tests, skip write to sysroot (noexec) and just package dbus-tests.
>>
>> 1. Do you guys know a better solution for this?
>
> It's actually the only solution that would work :)
>
>> 2. What would be a good path to use for installing tests?
>
> $bindir or $libexecdir IMO

Not bindir please!  Tests should live separate,

If it;s going to be libexecdir, really should be $libdir/$BPN as we want 
to move way from having things live in /usr/libexec, and yes with time 
$libexecdir will be $prefix/lib/$BPN.

Sau!


> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>

Re: dbus with tests

[Koen Kooi]

Op 14 aug. 2012, om 18:24 heeft Saul Wold <sgw@linux.intel.com> het volgende geschreven:

> On 08/14/2012 03:49 PM, Koen Kooi wrote:
>> 
>> Op 14 aug. 2012, om 13:11 heeft Andrei Gherzan <andrei@gherzan.ro> het volgende geschreven:
>> 
>>> In the process of updating dbus, tests (in my opinion) are mandatory.
>>> 
>>> While compiling dbus with tests, dbus and dbus-glib are needed. To compile dbus-glib, dbus is needed (obviously). The only solution (to compile dbus with tests) that i found is to create a new recipe named dbus-tests where to compile dbus with --enable-tests --enable-embedded-tests, skip write to sysroot (noexec) and just package dbus-tests.
>>> 
>>> 1. Do you guys know a better solution for this?
>> 
>> It's actually the only solution that would work :)
>> 
>>> 2. What would be a good path to use for installing tests?
>> 
>> $bindir or $libexecdir IMO
> 
> Not bindir please!  Tests should live separate,
> 
> If it;s going to be libexecdir, really should be $libdir/$BPN as we want to move way from having things live in /usr/libexec, and yes with time $libexecdir will be $prefix/lib/$BPN.

I wanted to suggest libdir/BPN, but since that's one of those new-fangled things adopted by systemd I thought people would have a knee-jerk reaction, kinda like the big players threatening to back out of yocto if systemd ends up in oe-core. 

Re: dbus with tests

[Burton, Ross]

On 14 August 2012 17:53, Koen Kooi <koen@dominion.thruhere.net> wrote:
> I wanted to suggest libdir/BPN, but since that's one of those new-fangled things adopted by systemd I thought people would have a knee-jerk reaction, kinda like the big players threatening to back out of yocto if systemd ends up in oe-core.

Debian's (and others) been using /usr/lib/$package instead of
/usr/libexec since, well, forever.

Ross