Mailing List Archive: Maemo: Developers

Optifing - Clarification Requested

Index | Next | Previous | View Threaded

nathan at andersonsplace

Oct 18, 2009, 3:56 AM

Post #1 of 4 (802 views)
Permalink

Optifing - Clarification Requested

Ok, I believe I have read all the messages; the talk thread and the wiki;
and I'm still a bit confused because of python issues.

I will be pushing several libraries that are in the end depended upon by a
custom swig generated python binding that a python app will be using.

Basically:

Lib-Sword -> (depends on)
lib-ICU
Lib-Clucene
lib-Curl (Already on device I believe)

Now I will be generating a python binding to the Sword library and it
generates a "_Sword.so" which the python app will use to handle everything.

Now for Optifing question:
1. can I optify Clucene, & ICU?
2. can I optify the main libsword?
3. do I optify the _Sword.so?

And what exactly do I need to do to set these as being or not being
optified.

I have everything running fine on the SDK. Basically I need to know the
packaging requirement to put them into Extras-testing.

Nathan

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

bundyo at gmail

Oct 18, 2009, 5:32 AM

Post #2 of 4 (741 views)
Permalink

Re: Optifing - Clarification Requested [In reply to]

There is libicu in extras-devel already, but it is not optified. libicu is
around 16MB+, so it better be. It won't get through testing with that size.

Regards:
Bundyo

On Sun, Oct 18, 2009 at 1:56 PM, Nathan Anderson
<nathan [at] andersonsplace>wrote:

> Ok, I believe I have read all the messages; the talk thread and the wiki;
> and I'm still a bit confused because of python issues.
>
> I will be pushing several libraries that are in the end depended upon by a
> custom swig generated python binding that a python app will be using.
>
> Basically:
>
> Lib-Sword -> (depends on)
> lib-ICU
> Lib-Clucene
> lib-Curl (Already on device I believe)
>
> Now I will be generating a python binding to the Sword library and it
> generates a "_Sword.so" which the python app will use to handle everything.
>
> Now for Optifing question:
> 1. can I optify Clucene, & ICU?
> 2. can I optify the main libsword?
> 3. do I optify the _Sword.so?
>
> And what exactly do I need to do to set these as being or not being
> optified.
>
> I have everything running fine on the SDK. Basically I need to know the
> packaging requirement to put them into Extras-testing.
>
> Nathan
>
>
> _______________________________________________
> maemo-developers mailing list
> maemo-developers [at] maemo
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>

anderson.lizardo at openbossa

Oct 18, 2009, 8:39 AM

Post #3 of 4 (730 views)
Permalink

Re: Optifing - Clarification Requested [In reply to]

On Sun, Oct 18, 2009 at 6:56 AM, Nathan Anderson
<nathan [at] andersonsplace> wrote:
> Basically:
>
> Lib-Sword -> (depends on)
> lib-ICU
> Lib-Clucene
> lib-Curl (Already on device I believe)

I think all the last three are already on extras-devel, but I'm not
sure about libclucene. libcurl is certainly there (as is pycurl, the
Python binding that the PyMaemo team maintains).

> Now for Optifing question:
> 1. can I optify Clucene, & ICU?
> 2. can I optify the main libsword?
> 3. do I optify the _Sword.so?

I think all three can be optified (the issues with Python are mainly
around the core Python package that installs python itself and
applications written in python that optify their main script), but the
best way to know it is to try it yourself: install maemo-optify on
scratchbox, build all the packages you need and optify their .debs.
Then, install the optified .debs and see if your application still
works.

> And what exactly do I need to do to set these as being or not being
> optified.

Maybe someone else that was on the Maemo summit can answer better, but
I think the current situation is that there is not automatic
optification (i.e. on the autobuilder side) in place at the moment. So
if you want your package optified NOW, you will need to change your
packaging to call maemo-optify on debian/rules (BTW, does any know of
instructions on how to do that?)

PS: In the end I believe the extras-testing QA will detect most of
issues with optified packages that do not work, simply because the
applications break in obvious ways. But I think it is a good idea to
each developer try out optification in their packages locally, do some
simple testing and report the issues found here. From the Maemo summit
BoF notes, it _seems_ many developers haven't tried maemo-optify on
their packages yet.

Regards,
--
Anderson Lizardo
OpenBossa Labs - INdT
Manaus - Brazil
_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

nathan at andersonsplace

Oct 18, 2009, 8:43 AM

Post #4 of 4 (727 views)
Permalink

RE: Optifing - Clarification Requested [In reply to]

Ok, you are correct -- I went into the Extras-Devel and you are correct
ICU 4.0 is on their -- I'm not sure why I missed it the first time. Is
their anyway we can figure out who uploaded it; as 4.21 is what is current
-- I don't want to step on others toes by uploading things that they are
maintaining. I pulled down the 4.0 package but the changelog had only the
original debian maintainer instead of the person who maemofied it. ;-)

As a small "aside" for Optifing things; is this a potential hole -- can
they get through "testing" if something else auto-promotes it, afaik. So
If I drop a small app that relies on icu, and it gets promoted then its
dependancies will be auto-promoted? Am I correct?

As for my original question; it isn't answered -- I've read emails
saying somethings with python should not be optified. I'm trying to
understand what can be and what can't be. And how to I triggue the
behavior?

Nathan.

_____

From: Kamen Bundev [mailto:bundyo [at] gmail]
Sent: Sunday, October 18, 2009 7:32 AM
To: Nathan Anderson
Cc: maemo-developers [at] maemo
Subject: Re: Optifing - Clarification Requested

There is libicu in extras-devel already, but it is not optified. libicu is
around 16MB+, so it better be. It won't get through testing with that size.

Regards:
Bundyo

On Sun, Oct 18, 2009 at 1:56 PM, Nathan Anderson <nathan [at] andersonsplace>
wrote:

Ok, I believe I have read all the messages; the talk thread and the wiki;
and I'm still a bit confused because of python issues.

I will be pushing several libraries that are in the end depended upon by a
custom swig generated python binding that a python app will be using.

Basically:

Lib-Sword -> (depends on)
lib-ICU
Lib-Clucene
lib-Curl (Already on device I believe)

Now I will be generating a python binding to the Sword library and it
generates a "_Sword.so" which the python app will use to handle everything.

Now for Optifing question:
1. can I optify Clucene, & ICU?
2. can I optify the main libsword?
3. do I optify the _Sword.so?

And what exactly do I need to do to set these as being or not being
optified.

I have everything running fine on the SDK. Basically I need to know the
packaging requirement to put them into Extras-testing.

Nathan

_______________________________________________
maemo-developers mailing list
maemo-developers [at] maemo
https://lists.maemo.org/mailman/listinfo/maemo-developers

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads