The documentation of this package is primarily the examples it provides. The uncompressed directories and pre-processed makefile are left in the /var/tmp/portage. I modified the ebuild to move these to the /usr/share/doc/${P} directory so that people can run the make file and check out the examples.
Created attachment 125705 [details] Upgraded ebuild to expand examples into /usr/share/docs/${P} I needed the examples and thought others might appreciate this ebuild upgrade.
Installing this cruft should definitely be optional (USE=examples or whatever).
In a lot of packages where the examples are just extra, I agree. I can certainly add this. But in this case they are heavily referred to in the man pages. The normal install unpacks these but doesn't run the make. As I have done here. I just moved them out of the tmp directory so they are not lost. I think that becuase this is a library for writing C apps that they should be included as the author intended. The tarfile provided should provide the same functionality via portage and otherwise. I needed them. I will let others discuss the options but rather than a use flag I would rather see a cdk and cdk_dev ebuild in that case. Then they show up in en emerge --search and you know what you are missing. PS, this is a small package but an improvement can be made in that I copied over the include directory so the relative include path works in the make for the examples. about 3/4 of the includes are copied to /usr/include/cdk but the other 1/4 are needed for the examples. Coping only the 1/4 that are needed will be my next improvement.
Done with use examples
