Re: [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE.

Re: [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE.

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

pfalcon commit schreef:
> removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE. 
> * Suggested by Marcin Juszkiewicz

>  Proposed by:    Koen Kooi
                   ^^^^^^^^^
If you're going to sneak in that commit when I'm offline at least have the decency to
notify me explicitly, so I know to do push the removal cset.

You're free to re-add the fixed version that doesn't break apps depending on bluez-libs,
but not the broken version.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFfxGRMkyGM64RGpERAsFGAJ9mjlQhjzqkHdgyyXng4EsMeE4YZwCcDsyf
/c2lRE3VVUOLqlXbnhz9beg=
=y1bm
-----END PGP SIGNATURE-----

Re: [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE.

[Paul Sokolovsky]

Hello Koen,

Tuesday, December 12, 2006, 10:31:13 PM, you wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> pfalcon commit schreef:
>> removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE. 
>> * Suggested by Marcin Juszkiewicz

>>  Proposed by:    Koen Kooi
>                    ^^^^^^^^^
> If you're going to sneak in that commit when I'm offline at least have the decency to
> notify me explicitly, so I know to do push the removal cset.

  Well, I don't sneak anything, that's nothing but indeed a concurrent
(or close to concurrent) update. As commit message tells, that move was
suggested by Marcin in a private mail. And yes, I wanted to cc: you,
but after all, I thought that he speaks as OE maintainer too, so you
likely have that communicated already.

> You're free to re-add the fixed version that doesn't break apps depending on bluez-libs,
> but not the broken version.

  I'll probably will eat my dogfood of maintainer of a bit bitrotted
stuff, and won't put outdated stuff back, but will look into
upgrading OPIE to bluez3, when I get to that.

> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)

> iD8DBQFFfxGRMkyGM64RGpERAsFGAJ9mjlQhjzqkHdgyyXng4EsMeE4YZwCcDsyf
> /c2lRE3VVUOLqlXbnhz9beg=
> =y1bm
> -----END PGP SIGNATURE-----


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com

Re: [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE.

[Michael 'Mickey' Lauer]

Paul Sokolovsky wrote:
>> You're free to re-add the fixed version that doesn't break apps depending on bluez-libs,
>> but not the broken version.

>   I'll probably will eat my dogfood of maintainer of a bit bitrotted
> stuff, and won't put outdated stuff back, but will look into
> upgrading OPIE to bluez3, when I get to that.

Not much action in upgrading necessary. The issue was (and still
remains) that bluez3 depends on dbus which in turn brings glib with it
and this is relatively huge.

The advantage of Opie fitting into 14.5MB flash like on Sharp SL5500 would
be void then.

Regards,

:M:
-- 
Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de

Re: [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE.

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael 'Mickey' Lauer schreef:
> Paul Sokolovsky wrote:
>>> You're free to re-add the fixed version that doesn't break apps depending on bluez-libs,
>>> but not the broken version.
> 
>>   I'll probably will eat my dogfood of maintainer of a bit bitrotted
>> stuff, and won't put outdated stuff back, but will look into
>> upgrading OPIE to bluez3, when I get to that.
> 
> Not much action in upgrading necessary. The issue was (and still
> remains) 

actually, no

>that bluez3 depends on dbus which in turn brings glib 

No, dbus doesn't bring in glib since dbus >0.71, since the bindings were split out:
http://www.angstrom-distribution.org/repo/?action=details&pnm=dbus-1

> with it
> and this is relatively huge.

See above

> The advantage of Opie fitting into 14.5MB flash like on Sharp SL5500 would
> be void then.

You couldn't have done that anyway with the change to rtti and qte-mt.

So it it seems all the points raised aren't valid anymore.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFfxopMkyGM64RGpERApgvAKCsfKbx4uhfBJEOT+Lp1JyE6niXDgCfazOi
RzO6LMU5oKmULqsGnj99xcY=
=+HA+
-----END PGP SIGNATURE-----

Re: [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE.

[Marcin Juszkiewicz]

Dnia wtorek, 12 grudnia 2006 22:00, Michael 'Mickey' Lauer napisał:

> The issue was (and still remains) that bluez3 depends on dbus which in
> turn brings glib with it and this is relatively huge.

obexpush already brings libglib-2.0-0 - someone had patch for it iirc

And dbus *NEED* more granular packaging - dbus-1 package is 440K unpacked 
where 230K is dbus-daemon itself and OPIE images need only 
lib/libdbus-1.so*

> The advantage of Opie fitting into 14.5MB flash like on Sharp SL5500
> would be void then.

OPIE from .dev already is hard to fit - qte-mt with Japanese support is 
larger.

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

             Today is the first day of the rest of your life.

Re: [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE.

[Marcin Juszkiewicz]

Dnia środa, 13 grudnia 2006 08:51, Marcin Juszkiewicz napisał:
> Dnia wtorek, 12 grudnia 2006 22:00, Michael 'Mickey' Lauer napisał:

> > The advantage of Opie fitting into 14.5MB flash like on Sharp SL5500
> > would be void then.

> OPIE from .dev already is hard to fit - qte-mt with Japanese support is
> larger.

16.469.224 opie-image-collie-20061213112019.rootfs.jffs2

Thats openzaurus-unstable/collie build of today. 

OPIE is hard to build from .dev - rtti/no-rtti problems from time to time 
(opie-alarm/qcop/rdesktop are not buildable without linking with g++ or 
changing CFLAGS).

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

             I do not fear computers. I fear the lack of them.
             		-- Isaac Asimov

Re: [oe-commits] org.oe.dev removal.txt: Push bluez*2.* removal to a month later, as it is known to be used by OPIE.

[GoXbox Live]

That't the same happening when using Familiar as distro.
But when building with Angstrom as distro it builds with no hacks.

goxboxlive

2006/12/13, Marcin Juszkiewicz <openembedded@hrw.one.pl>:
>
> Dnia &#65533;roda, 13 grudnia 2006 08:51, Marcin Juszkiewicz napisa&#65533;:
> > Dnia wtorek, 12 grudnia 2006 22:00, Michael 'Mickey' Lauer napisa&#65533;:
>
> > > The advantage of Opie fitting into 14.5MB flash like on Sharp SL5500
> > > would be void then.
>
> > OPIE from .dev already is hard to fit - qte-mt with Japanese support is
> > larger.
>
> 16.469.224 opie-image-collie-20061213112019.rootfs.jffs2
>
> Thats openzaurus-unstable/collie build of today.
>
> OPIE is hard to build from .dev - rtti/no-rtti problems from time to time
> (opie-alarm/qcop/rdesktop are not buildable without linking with g++ or
> changing CFLAGS).
>
> --
> JID: hrw-jabber.org
> OpenEmbedded developer/consultant
>
>              I do not fear computers. I fear the lack of them.
>                         -- Isaac Asimov
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>