On Friday 02 April 2010 22:59:58 Thiago Macieira wrote:
> Em Sexta-feira 2. Abril 2010, às 23.45.16, Graham Cobb escreveu:
> > On Friday 02 April 2010 21:45:27 Auke Kok wrote:
> > > Our policy was/is to support all the major distros. Nothing more,
> > > nothing less.
> > >
> > > We want people to be able to build MeeGo images on any current and
> > > popular distro. Period. No exceptions.
> >
> > Good news, thank you.  Bug 446 logged.  Any idea when it is likely to be
> > fixed?
>
> Why did you file it in bugzilla.meego.com? How is it MeeGo's problem that
> Debian doesn't have python-kickstart?

Did you read the bug?

1) Auke stated that it is MeeGo policy that they "want people to be able to 
build MeeGo images on any current and popular distro".  Assuming that is 
really MeeGo policy then it is a bug that it is not currently possible on 
Debian.

2) The main issue is that the instructions in 
http://wiki.meego.com/Developing_in_a_Meego_Environment don't work.  That is 
a bug in the instructions.

3) Is it MeeGo's problem that Debian doesn't have mic-chroot?  Yes.  So, MeeGo 
provides it.  python-kickstart is no different.

> You should file that to Debian and ask them how soon they can provide a
> package.

That is not how distros work (any distro, not just Debian) -- if I create an 
app which I want to work on Debian, it is my responsibility (not Debian's) to 
provide all the dependencies which are not part of the distro.  If I want to 
create packages for (say) GPE on Debian, I can't complain that Debian hasn't 
packaged some library I need -- I have to include packages for that with my 
release as well.

There is nothing special about Debian here -- it works the same way on (say) 
Fedora, or even MeeGo!  When I port GPE Calendar to MeeGo I won't be logging 
a bug against MeeGo that it doesn't include libgpepimc -- I will be porting 
that as well. Similarly, if I wanted to port kontact to MeeGo, I wouldn't 
report a bug that libkdepim4 wasn't available in MeeGo!

It is clear it this is a MeeGo bug -- I don't think anyone from the MeeGo 
developer support team will disagree.  Of course, we are here to find bugs so 
that is no problem.  That is why I asked for a workround (and thanks to Samir 
for providing some steps towards one -- but that is the subject of another 
email).

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

Reply via email to