[maemo-developers] New release of Python2.5 for Maemo (r0.4-11)

[From: Kees Jongenburger]

On 6/28/07, Riku Voipio <riku.voipio at movial.fi> wrote:
> MoRpHeUz wrote:
> >   Great applications like Carman, Konttouri's player and others were
> > written in python. And the final users wont have this applications
> > working well if we dont have python support for the platform.
> >
> Why would that need python support *in* the platform? It should jsut be
> a matter
> of putting ukmp and pymaemo in maemo extras and having a proper install file
> for ukmp.
>
> I see it's not true for now.
>
> 1) pymaemo needs clicks on two install files "base repo" and "pymaemo" why?
> Which basically  foils down either limits in .install files and/or
> problems with using
> garage. Next time someone is going to write a neat ruby application, it
> needs to be easily
> installable as well, and you can't solve all dependency problems by
> adding everything
> to official(tm) firmware.

I guess it is just a matter of taste and real support. I don't like
the debian taste , I don't like the python taste , I don't like the
gnome/gtk taste but I love the maemo platform.
I think maemo was really lacking scripting/RAD support. Just porting
ruby was relatively easy but having a desktop that is ready to get
scripted just takes a lot more work(and specially those non
python/ruby guys who spend time creating bindings etc). I have this
feeling that the python choice was made years ago and I could very
well live with it. Even stronger I would prefer the maemo community to
just make clear choices. In that manner I can like it and be happy or
dislike it and start porting other things but there should be at least
one very well supported RAD /scripting language so why not put it on
the device.

> 2) ukmp does not have a install file, but a .deb. according to
> maintainer uploading
> to extras is "too hard"
>
> ^ those are the issues that need fixing, not adding arbitrary bloat[1]
> to the base system.

isn't it just the base system that is bloated and therefore requires such
weird steps?

it is not easy to upload to the extra repository because it simply takes a
debian based install + a debian maintainer to perform this black art
of packaging and uploading. I think that the platform really needs
some improvement here but I am no sure there is a fix for this. also
contributing to base packages is very hard if not impossible.

but keep up python alive!

greetings