Re: [Gnucap-devel] git repo proposal

[al davis]

On Sunday 26 May 2013, Felix Salfelder wrote:
> i have a draft for including plugin package-tarballs into the
> build system within the autotools-WIP branch. basically it
> works like 1) place your package into <gnucap-src>/extern
>    type
>           git clone <gitrepo> extern/<name>
>           cd !$; ./autogen.sh; cd -
>         or just
>           tar -xf <tarball> -C extern/<packagename>
> --strip-components 1 2) run ./configure (once)
> 3) (todo) make check, install now dives into externals

I saw that ...  I really don't want to use autotools for this.  
Aside from that I think autotools is such a mess, compiling and 
installing plugins is something a regular user should be able to 
do.

Consider this ....  There's a computer lab in an undergrad only 
university.  Let's assume they have some linux distro. how about 
CentOS for now (very stable, not much in the library).  They 
have installed gnucap by "yum install ...", and the sysadmin is 
clueless about what else is needed.

Now a student wants to use those models.  The command should be 
"load path/to/modelsourcedir".   and nothing more.


> all we need is one git repo for each plugin-package. i have
> gitified gnucap-bsim gnucap-spice3f5 gnucap-geda gnucap-adms
> and gnucap-bm (i certainly need some help making all of them
> work.)

That's what I mean.