this is what my intention was as well, but nobody confirmed when I asked
about it. I'll prepare another patch.
Radu
On 07/30/2012 06:07 PM, Burton, Ross wrote:
On 30 July 2012 12:24, Radu Moisan wrote:
+PROVIDES = "dbus-x11"
The provides that provide comparability were RPROVIDES/RREPLACES,
On 30 July 2012 12:24, Radu Moisan wrote:
> +PROVIDES = "dbus-x11"
The provides that provide comparability were RPROVIDES/RREPLACES, this
doesn't do anything because nothing should be DEPENDing on dbus-x11,
so you can remove it.
Ross
___
Openembedded-
Followed suggestions from Bugz 2261:
2) make the virtual/libx11 DEPENDS conditional based on the x11 distro feature.
This makes the build dependencies reflect the feature list.
3) remove dbus-x11, meaning that dbus-launch with its potential X11 dependency
is now back in dbus where is belongs.
4)
Op 25 jul. 2012, om 16:23 heeft Paul Eggleton het volgende geschreven:
> On Wednesday 25 July 2012 15:19:10 Burton, Ross wrote:
>> On 25 July 2012 15:17, Koen Kooi wrote:
>>> This breaks the upgrade path
>>
>> So how would the upgrade path be unbroken? A dummy dbus-x11 package
>> that pulls in
On 25 July 2012 15:23, Paul Eggleton wrote:
> On Wednesday 25 July 2012 15:19:10 Burton, Ross wrote:
>> On 25 July 2012 15:17, Koen Kooi wrote:
>> > This breaks the upgrade path
>>
>> So how would the upgrade path be unbroken? A dummy dbus-x11 package
>> that pulls in dbus, I suspect.
>
> RREPLA
On Wednesday 25 July 2012 15:19:10 Burton, Ross wrote:
> On 25 July 2012 15:17, Koen Kooi wrote:
> > This breaks the upgrade path
>
> So how would the upgrade path be unbroken? A dummy dbus-x11 package
> that pulls in dbus, I suspect.
RREPLACES_${PN} += "dbus-x11" ought to be enough...
Cheers,
On 25 July 2012 15:17, Koen Kooi wrote:
> This breaks the upgrade path
So how would the upgrade path be unbroken? A dummy dbus-x11 package
that pulls in dbus, I suspect.
Ross
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
Op 25 jul. 2012, om 16:03 heeft Radu Moisan het volgende geschreven:
> Followed suggestions from Bugz 2261:
>
> 1) remove the --with-x/--without-x configure arguments. If you want to force
> no-discovery for native builds the correct argument is
> --disable-x11-autolaunch.
> This ensures that D
Op 25 jul. 2012, om 15:58 heeft Phil Blundell het volgende geschreven:
> On Wed, 2012-07-25 at 17:03 +0300, Radu Moisan wrote:
>> +# for compatibility
>> +RPROVIDES = "${PN}-x11"
>
> ITYM RPROVIDES_${PN}. Isn't that a QA error?
Sadly not, you need to run kergoths recipe_sanity manually to catc
On Wed, 2012-07-25 at 17:03 +0300, Radu Moisan wrote:
> +# for compatibility
> +RPROVIDES = "${PN}-x11"
ITYM RPROVIDES_${PN}. Isn't that a QA error?
p.
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtog
Followed suggestions from Bugz 2261:
1) remove the --with-x/--without-x configure arguments. If you want to force
no-discovery for native builds the correct argument is --disable-x11-autolaunch.
This ensures that DBus looks at the build environment to determine whether to
enable X11 bus discovery
11 matches
Mail list logo
