Hi! Please find attached tcl-8.3.3.ebuild and tk-8.3.3.ebuild. These ebuilds accomplish the following: 1. split the tcl and tk packages into separate ebuilds. This makes writing ebuilds for packages that depend on tcl and/or tk much easier to handle (see expect-5.33.0.ebuild post and the vim-6.0-r2.ebuild patch attached). I recommend putting the tcl ebuild under dev-lang/tcl and the tk ebuild under dev-tcltk/tk. 2. ebuilds are now version independent. Renaming ebuilds to *-8.4.2.ebuild should work. I have not tested this, but these ebuilds were based on the tcl-tk-8.4.2.ebuild. 3. The original tcl-tk-8.3.3.ebuild did not install the private headers and config.sh's for tcl and tk. This is why vim-6.0-r2.ebuild did not work with 'use tcltk' 4. Promotes world peace and smells minty fresh. Splitting up tcl and tk into separate ebuilds may cause some minor pain updating the dependencies of ebuilds that depend on them, but I think it is worth it in the long run. tod
Created attachment 13 [details] tk-8.3.3.ebuild
Accepting as a real bug. I'm testing the ebuilds out on my system.
It works for me, so I'm committing the ebuild.
Hi! Some additional info that might be of use. 1. The expect ebuild (bug 28) is a good test of a working tcl and tk installation. It depends on tcl-8.3* and tk-8.3*, but won't compile because the private headers are not installed by the current tcl-tk ebuild. 2. Contrary to my original comments, the submitted tcl-8.3.3 ebuild does not fix the vim --with-tcl problem. It does allow vim to be compiled successfully using the --with-tcl configure flag and the resulting vim appears to run fine, however it doesn't pass the VIMINIT='let OS = system("uname -s")' vim test that agriffis pointed out to me (see vim-6.0-r3.ebuild) This appears to be an upstream vim issue. tod
