Hi,

On Thu, Jul 1, 2010 at 6:48 PM, Bridgette <[email protected]> wrote:

> The repo has multiple rpm's...is this how the source code available? It is
> not available altogether in one download?
>

I don't believe there is a single download with the source code of all the
project components. As with any other FOSS project you can find the
individual revision controlled repos for the components. You also can
get the source RPMs (*.src.rpm) under the respective 'source' dir in
http://repo.meego.com/ These can be installed in a RPM-based system
and built. Useful if you are trying to build/rebuild RPM packages from
those. In short these are RPM package repositories.


>
> I'm a bit confused when it comes to the images, the separate repository (
> http://repo.meego.com/) and then the git repository (
> http://meego.gitorious.org/)....despite<http://meego.gitorious.org/%29....despite>reading
>  the wiki (
> http://wiki.meego.com/Developer_Guide) I'm still not quite sure.
>

I'm not sure what you exactly mean. I'm assuming you are confused
about what's in each different location. As for the r.m.c see the above.
http://meego.gitorious.org/ hosts the version controlled (Git) source
code repositories (opposed to RPM repos) where MeeGo systems
developers collaborate.

I agree that the 'Developer Guide' page and http://meego.com/developers
pages aren't quite distinguishing between MeeGo system developers
and the Application Developers for MeeGo. Somebody who can make
changes to the main web have to make it happen on the main web site.

As for your subject, those pages mainly point you to places where you
should refer if you are an application developer.


>
>
> Thanks...
> Bridgette
>
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
>
Hope this is what you were trying to understand.


-- 
Gaveen Prabhasara
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to