On Mon, Jul 10, 2006 at 12:57:08PM +0000, Olafur Jens Sigurdsson wrote: > Hi, I agree with Mark in that it is a little unintuitive.
I'll reiterate my invitation to document such things as you find the need. Many of them already are though, and only the people who get stuck can fill in what they found missing. Many, many, people seem to have no problem. So we can't be too far off, I hope... > Specially since the man page for wx-config is in the wx-common package Should not be surprising, it is common to all the things that depend on it. > but the executable is in another package Uh, there is no executable matching the name of the man page. `man update-alternatives` then see the bit about _common_ again. > and the wx-common package doesnt reference the -dev package There are many dev packages, it is common to them all and depends on none of them. If you want to build against a library, step 1 has _always_ been, install its -dev package. If you don't get that far, more documentation in this package is going to lead to a lot of basic repetition. We need to toss you a line at some earlier point in the process. > and nothing about it in the documentation for the wx-common package. Did you read so much as the package description for wx-common? I don't see anywhere it might lead you to believe the things that are being professed it should do. If it does, please suggest text to dispel this myth and I will put it to rest at once. This is NOT an 'sdk' metapackage, it is a collection of miscellaneous odds and sods that don't belong in any particular package, but may be used or required by several of them. I thought that was pretty clear. If it's not, lets fix it up, ok? Patches welcome. thanks, Ron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
