[MeeGo-dev] Building the Meego Dev Environment
auke-jan.h.kok at intel.com
Mon Apr 5 14:48:17 CDT 2010
On 04/03/10 01:16, Jean-Christian de Rivaz wrote:
>> > Actually, bug 446 is about the meego instructions, which are indeed
>> > lacking. Glancing over it, I only see references to FC, nothing else, so
>> > that certainly needs fixing.
>> > A separate bug report to debian, or better, someone who knows python and
>> > debian packaging submitting a pykickstart package to debian, would help
>> > a ton though, and yes, we don't have anyone testing this at the moment I
>> > think, and that's also an issue, but perhaps not so high priority.
> If I understand you correctly, supporting Debian Lenny (Stable), in not
> a high priority. A bit the contrary of "supporting every distribution
> out there". The situation is currently at least confusing for a user
> like me.
how is that contrary? Supporting other distro's is way below all the
release work and development work as long as none of the code is mature,
so -other- distro support will always be behind fixing plain bugs.
There's nothing contrary about that.
As for everyone here, people are crunching on QA and the upcoming
releases. I'm very sorry that we don't have a slick development platform
out there for <distro>, but there's only so much we can do.
Here's how you can improve: (remember this is a community effort?)
- package the missing parts from debian if you're a debian user, submit
to debian. We don't have any debian developers here in my office really.
I wonder what all those people with @debian.org e-mail addresses on the
mailing list could do for us?! They seem to be so vocal on the list,
perhaps they have some extra time ;D.
- document the issue with <distro> in the wiki, investigate a workaround
and provide instructions
- help us get through the development phase by debugging the image
creator on MeeGo and make it mature, so we can move to debugging on more
platforms quicker. We're not going to debug how the image creator works
on <foo> if it still has lots of bugs against <meego>.
does this not make any sense? It seems so obvious to me.
More information about the MeeGo-dev