Joe English wrote:
> As a matter of fact (AIUI -- dgp, please correct me if I'm wrong)> one of the prerequisites for inclusion under tcl/pkgs/ is that there> be an official released tarball. So no worries there: independent> releases of everything under tcl/pkgs/ will always be available,> by policy.
That's the plan. We've fudged the issue slightly with tdbc because
1) these are the first releases of tdbc, so the process there is
still getting formed;
2) projects kept in fossil, like tdbc, to my eye appear a bit unusual
about releases. I can't decide if everything is a release, or
nothing is. Suffice to say everything we've called a release and
put onto the vendor branch corresponds to (a portion of) a zip file
available online to anyone;
3) Simple favoritism, since it's kbk we're dealing with.
But once the system is well established, that's the intended policy,
yes. Redistribute only unchanged copies of third party releases.
> My preference would be for two Tcl tarballs; a "BI" version> with pkgs/ fully populated and a "naked" version that has> just Tcl and only Tcl.
I don't object to that. I'll have the pieces anyway, so making them
available for separate download isn't a large additional burden.
The actual value of this is not as clear to me as it is to others,
but if it will help people and doesn't take too much effort, I don't
see a reason to say no.
--
| Don Porter Mathematical and Computational Sciences Division |
| dona...@nist.gov Information Technology Laboratory |
| http://math.nist.gov/~DPorter/ NIST |
|______________________________________________________________________|
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Tcl-Core mailing list
Tcl-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tcl-core