[Tcllib-devel] TBWidget Branch (please help on cvs organisation)

[Harald O. <Har...@El...>]

Hi community,

**I would apreciate, if a tcl-lib expert would answer the question at
the end of this e-mail**

as announced in my email on this list:
Subject: [Tcllib-devel] BWidget verification, tagging and TBWidget
Date: 2009-07-20

it is planed to branch BWidget into two source trees:
- BWidget - use tk8.1 and later, no ttk code
- TBWidget - use ttk8.5 and later, no tk and tcl8.1-8.4 code

Why two source trees ? It is a real split of scope.
BWidget is complicated enough. To support ttk and tk, many code will be
doubled. In addition, I don't want to drop tk8.1 compatibility, but many
things just would be more elegant and some work-arounds will go away.

I am in doubt on the cvs level how to do this.

Two alternatives:

1) use module bwidget and put TBWidget into a branch

How to branch:

cvs -z3 -d:ext:oe...@tc...:/cvsroot/tcllib rtag -b
-r bwidget-1-9-0 tbwidget bwidget

How to checkout:

cvs -z3 -d:ext:oe...@tc...:/cvsroot/tcllib
checkout -r tbwidget -P bwidget

Advantage: all history kept
Disadvantages:
- No head revision for tbwidget
- Have to specify -r tbwidget on all operations for tbwidget

2) Create a new module tbwidget

cvs -z3 -d:ext:oe...@tc...:/cvsroot/tcllib import
tbwidget oehhar tbwidget

Advantage: Own head revision for BWidget and TBWidget, much clearer
Disadvantage: file history lost for TBWidget

3) do something else ???
Other ideas ? Migrate to subversion where this is not an issue ;-)

Properties of both solutions:
- No change for BWidget on the cvs level

Thank you for any insights.

Regards,
Harald