2010/6/21 Dave Neary <[email protected]>:
> Hi,
>
> Thiago Macieira wrote:
>> Em Domingo 20. Junho 2010, às 20.25.18, Tomasz Sterna escreveu:
>>> - Do you really consider yourself Open, if nobody outside your paid
>>> developers ring could build a MeeGo distribution image?
>>
>> That's a stupid question. Bugs aren't there intentionally to keep you from
>> working.
>
> Clearly he was talking about "essential packages are missing to allow me
> to build the image. These were removed from the codedrop repos, but are
> not shared anymore because they share new Handheld UI repo" - which was
> a new one on me, but if true, then the question is very legitimate.

That one was a misunderstanding discussed afterwards on IRC.

The codedrop repositories were removed for some weird reason and hence
old kickstart files, amongst others, our old codedrop closed source
kickstart files stopped being able to build. And we don't have a MeeGo
1.0 closed image because of problems with battery charging with
2.6.33. If we have had that, there would be no problems whatsoever,
but safety comes first.

There was a discussion between if hardware specific packages should be
in Trunk or seperate and hence our N900 support packages weren't yet
in Trunk (coming on thursday latest, according to the weekly cycle),
hence you couldn't use the daily Trunk builds.. :) A bit of a bad
situation, agreed. But a timing issue.

The mention to Handheld UI is due to the fact OBS live URL is still
off limits due to Handset UX big reveal, but I'm sure you all know my
opinion on this matter. And the OBS live URL includes, amongst others,
our devel:devices:n900 repositories which would have solved the
current problem of not having access to those packages.

Hopefully all these non-openness problems will be over soon, as
they're really starting to badly affect our daily work.

Tomasz's main point is that MIC2 is acting really erratic outside
Fedora or MeeGo OS'es. It is something we need to take up. We need to
have top notch tools and a direct access to making images on your own
if we want to see MeeGo succeed. Big hassle will scare away vendors
and hobbyists.

Best regards,
Carsten Munk
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to