Re: [Gnucap-devel] savannah git repositories

[al davis]

On Sunday 14 September 2014, Felix Salfelder wrote:
> i considered what happened so far
> as a workaround. 

it is.

> also, i somehow expected that the extra
> branches were intended to be merged into master finally (and
> i now learned that this is probably wrong).

Part of the intent of plugins is to make available stuff that 
may have limited appeal, may be work-in-progress, may have 
dependencies, may be of low quality,   ......   or any of a 
number of reasons keep it separate.

It's hard to know up front what will eventually be merged into 
master.

Predictions:

gnucap/adms
        Never.  ADMS is a separate project.  Ideally, it would have 
its own site, and its targets would live there, like gnucap 
plugins.  Then we would link to it.  It doesn't seem to be that 
way.  NGspice has its own, Qucs has its own, Xyce has its own, 
and it seems the master isn't maintained.

gnucap/gui
        At this point it needs to be separate because of the 
dependency on a specific graphics library.

gnucap/plugins-models
        This changes faster than master and always will.  It may 
make sense to separate spice (the past) from verilog (the 
future).  Almost all new work in modeling is done in verilog-
ams.

gnucap/bm
        I think this is a dead-end.

gnucap/modelgen-verilog
        I think this will eventually replace the old modelgen, 
maybe even ADMS.

gnucap/plugins.git
        The catchall for new stuff, mostly small.  This one could 
be an exception to the usual master, but maybe not.  How about 
... non-master branches are specific, not forks of master but 
rather forks of nothing.   Then master is a merge of all of 
them.  There could be several master-like branches, something 
like "stable", "testing" and "unstable".