On Tue, Jan 30, 2007 at 01:02:24PM +0100, [EMAIL PROTECTED] wrote: > I (or let say "we") really need these headers files to compile some python > modules which are not part of debian.
Who is "we"? Or shall we just stick to "you" ;-) > For now, I have a stupid workaround (just copy the missing files from another > source). Well, as I indicated previously, a fix was discussed and created on the wxpython-dev list, then rejected by Robin, effectively on the basis of "if stupid workarounds are good enough for Redhat, who cares about Debian" end of discussion. Until upstream supports installing them without stupid workarounds, they clearly don't consider them an important component. Hence in the absence of packages in the distro requiring them, pragmatically neither do I. > Ok, the python modules I'm was talking about are not part of Debian but > providing such a wx package with missing headers files is just pointless. That's a little melodramatic don't you think? There are plenty of dependant apps that get by just fine without them, and have done for many, many, years now. What probably _is_ pointless is worrying about this much for this particular release. Etch is freezing nicely, so we're unlikely to update it before it releases now, and with wx2.8 rushed out hot on its heels, 2.6 is likely to die quite quickly shortly after that, so the time for useful action on this seems to have well passed... If you want it fixed for 2.8 or later, you'll need to convince upstream of the importance of being able to include them as part of a binary package without the need for stupid workarounds. If you want to convince me of something otherwise, we're going to need to stick a little closer to some real facts about why this is important enough for me to care about while others don't. I don't have a lot of spare time for supporting vague unnamed packages that don't appear to be of enough value to the community to include in the distro. Doing that is what people have jobs for ;-) Sorry, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
