Summary: | the USE variable 'tcltk' *should* be 2 variables, 'tcl' and 'tk' | ||
---|---|---|---|
Product: | Portage Development | Reporter: | SpanKY <vapier> |
Component: | Unclassified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
SpanKY
2002-07-22 16:45:45 UTC
show me examples of where splitting it achieves your goall ill find some concrete examples, but i just dont like dev-lang/tk being on my server since its not useful wh00t, heres some i want tcl, i dont want tk, but if i have 'tcltk' in USE, then it installs dev- lang/tk for the following packages: dev-db/postgresql dev-lang/python (which means tk is on your system from the start :]) If you take a look at the postgresql ebuild you'll find that if "tcltk" is in USE then tcl will be installed as a dep, not tk. In the case of python tk will be installed as a dep, but that's because the default gui for python is "tkinter", which requires tk. To the best of my knowledge we have no packages that have both tk and tcl _optional_ functionality. If you find an exception, though, then we'll probably go ahead and separate tcltk into tcl and tk. Until then, though... ill reopen as soon as i have some more examples (even if i have to make & submit ebuilds myself :x) |