Em Sábado 3. Abril 2010, às 00.38.30, Graham Cobb escreveu: > On Friday 02 April 2010 22:59:58 Thiago Macieira wrote: > > 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.
Yes, it's a Debian bug that they don't have the package. Asking MeeGo to solve the bugs of every single distro out there is silly. It's all open source and it should build in any distro. If the software is authored and maintained by MeeGo and it won't compile or run properly in a given distro (provided all dependencies have been installed), then it's a bug. > 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. > 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. > > 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. If a distro wants to package my app, they'll include library A. If I want the distro to package my app, then I'll probably take the necessary steps to ensure that everything is proper, including the dependencies. If the distro won't package my app, then the users of that distro will need to get library A, install it, then my app, and install it. If that library won't install properly on that distro, it's also not my problem. It's Library A's author's problem and also the problem of the users of that distro. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Senior Product Manager - Nokia, Qt Development Frameworks PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
