[MeeGo-dev] Remote developing platform, remote building, personal/team repositories...
kate.alhola at nokia.com
kate.alhola at nokia.com
Thu Feb 18 08:38:12 CST 2010
>From: pan1nx at gmail.com [pan1nx at gmail.com] On Behalf Of ext Peter Antoniac [pan1nx at linux.com]
>Sent: Thursday, February 18, 2010 3:51 PM
>To: Alhola Kate (Nokia-FNDC/Helsinki)
>Cc: steve at lonetwin.net; michal at sawicz.net; meego-dev at meego.com
>Subject: Re: [MeeGo-dev] Remote developing platform, remote building, personal/team repositories...
>> Depends on case, simple application cases it could be even good choice.
>> Nokia has already as addition to maemo.org had "Qt remote compiler" tool
>> that can create both debian and .sis packages. This tool can be used
>> even without installing any device SDK to your computer.
>The whole idea behind this thread (remote building) is to avoid
>scratchbox/moblin image creator! The Qt remote compiler is cool, but
>it is not linked to SCM the way Launchpad/OBS are. It is just on the
>developer to see the result of the code compiled. My idea goes beyond
>that: you build, test, package, publish in repository, maintain
That's idea for the Forum Nokia Remorte compiler does already for Maemo and Symbian.
That won't need so complicated system at all.
I think that Meego buld environment should also offer similar functionality to developers ahare and
publish theis code as maemo.org extras/extras devel does
Idea is that when you would publish your sw, put it to autobuilder queue and and you (and the community) will
find package from extras-devel repository . When you are ready to send it to user testing, it will be promoted
to extras-testing and when it is approved, it goes to extras for all users download. At the moment it
does automatically x86 and ARM packages . There won't be so big work to make RPM also.
That extras builder has been big strength for maemo community. When you got your
device, you can see all community applications in your application manager ( if you enable extras ).
You don't need hunt them from dozens ef websites and then you end up package that does not work in your system.
When package is compiled with certain toolkit in maemo.org, it will work in the device.
If you can do this kind of system based on OBS, it is OK to me.
>>Anyways, bring my suggestion back on track -- what I meant to say is we allow
>>coders submit either debs or rpms or both to a build system (like for instance
>>OBS -- but *very* MeeGo aware) and the application manager *GUI* in Meego hides
>>away the lower level details for installing a package from the user -- in fact,
>>besides the rpm support, this is very much like how the Application Manager in
>>Maemo works, isn't it ?
> I think that this is a good idea.
>Yes. It will be THE BRIDGE of all the worlds: mobile - desktop,
ARM-X86, RPM-DEB should be doable but mobile-desktop has problem that UI need to be refactored
to be usable in mobile environment and this can't be automatized.
More information about the MeeGo-dev