Here is in ebuild I made for tclkit. I have not made many, but I tested this one and it seems to work for me. Here is a webpage describing tclkit: http://www.equi4.com/tclkit.html basically it allows you to run starkits, which are single file, all in one tcl applications. Reproducible: Always Steps to Reproduce: 1. try to emerge tclkit Actual Results: there is no tclkit ebuild Expected Results: tclkit should have installed, along with SDX (possibly depending on a new USE flag to determine this?). SDX allows you to edit starkits (website: http://www.equi4.com/sdx.html ) However, SDX is itself a starkit, and is thus run as 'tclkit sdx.kit <sdx command> <starkit-to-edit>'. so where to install sdx? Should we create a new /usr/local/lib/starkists directory to keep them? that would be a long path to type... This is why I have not included an ebuild for sdx, I don't know where it goes!
Created attachment 67903 [details] tclkit ebuild
OK, sorry but with nomirror *and* lack of version in tarball name, this is CANTFIX, because this breaks digests, so we would have to mirror it manually and we are not allowed to do so with nomirror. Even if the restrict was put into the ebuild by mistake, manual mirroring is something we try to avoid as much as possible. Contact upstream and ask them to ship tarballs that include a version number. Also, license is missing. If this is a binary-only package, then it belongs to /opt, not /usr/bin.
Closing CANTFIX unless the above issues can be solved.
