eclass/wxlib.eclass (bug #89937) copies the demos subdirectory into /usr/local/doc as part of the install. Perhaps it would be a good idea if it also copied over the samples directory too (by tweaking wxlib_src_install) - although this is more of use to developers than users, so maybe this should be controlled by a USE flag (I would have thought sdk would be idea, but it seems to be depreciated?) Reproducible: Always Steps to Reproduce:
Good idea, thanks. I also added the utils directory. Theres no strict policy but in general we just use the 'doc' flag for demos/samples, so it uses that. Adding to cvs as soon as I test it on another machine. p.s. You said /usr/local/doc but I hope you meant /usr/share/doc?
Correct, I meant /usr/share/doc instead of /usr/local/doc; my mind must be slipping due to low caffeine levels ;-) utils too. Excellent. Should the files in there be built too, or left as an exercise for the user? (For example, wxrc is quite useful on a development machine)
Ok, I committed the wxlib.eclass with samples and utils. wxrc is already installed as /usr/bin/wxrc-2.6, but it will probably be renamed to just wxrc (I was informed it works with 2.4 too). As for building the utils, for now I'll just install them not build them. On 2.4* some of the stuff wouldn't build and I'd hate to abort an emerge just because some odd utility isn't maintained upstream. I will leave this open and test the helpviewer in utils. Some people will probably want it and I'll test whatever else is in utils. Moving all the docs/utils/samples etc to a separate wxdocs package, in case it fails, might be a good idea, seeing how long wxGTK takes to emerge.
Ok, everything (samples/utils etc) are added with the 'doc' USE flag, but it doesn't build everything because theres too much unmaintained code there. If anyone finds a compelling reason to build something in particular (preferably with patches), feel free to reopen.
