Thiago Macieira wrote: >> 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. > > Yes, it's a Debian bug that they don't have the package. however 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.
So no, it's not; as Graham correctly observed earlier. >> 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. > > I understand now. It's just that the text you pasted in the bug report was > simply showing that you had not installed python-kickstart. Yeah, Debian has these wonderful things in packages called dependencies] :) If a package installs and doesn't work because another bit of SW is missing, that's a bug in the packaging for that distro. Not a user error. Who did the packaging for this app? Meego or Debian? Whoever did it got it slightly wrong - I really don't mind that at all. But denying responsibility.... that's what I have a problem with hence.... >> 3) Is it MeeGo's problem that Debian doesn't have mic-chroot? Yes. So, >> MeeGo provides it. python-kickstart is no different. > > No, it's not MeeGo's problem. > > It's Debian's problem that they didn't package it, or ultimately yours. > > Like I said, asking MeeGo to conform to the lowest common denominator in ALL > distros is silly. The software can be installed on those distros, so install > it. See "Depends:" I have a lot of respect for you Thiago - but in this you're dead wrong. About the only thing I can grant you is that if a Meego SDK app requires something that technically can't be installed in Debian or that, on balance, requires too much work; then it may no longer be supported on Debian. >>> 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. > > That's not how I understand. > > If I write an application and I use library A, that's that. I release my > application. Yes - that's why it's not a bug in the application. However this does not jibe with "Our policy was/is to support all the major distros. Nothing more, nothing less." David -- "Don't worry, you'll be fine; I saw it work in a cartoon once..." _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
