Re: Tcl/Tk source directories
In my Tcl/Tk packages, I have conformed to what I think is the
official Debian convention and renamed the source directories from
<package><baseversion> to <package>-<fullversion>. Unfortunately,
this causes gratuitous changes in other packages which need to access
the Tcl/Tk source directories. Since I try to make my Tcl/Tk patches
usable by other distributions (Slackware uses them and RedHat may
also, at least in part), this is very undesirable. Would anyone
object, if I reverted back to the original names as distributed by
Could you describe the problem a bit further?
[a] is there a reason not to solve this with soft links?
[b] is this an example of the "source as a development package" issue?
I'm not sure exactly what Dr. Ousterhout has set up, but it should be
noted that the debian package guidelines are primarily oriented
towards making it useful to have an automated (or easy) build process
for the packages. This is conceptually independent of what you have
to do for exported sources.
I think the linux kernel sources are our best model to date.