Re: gEDA-user: Alternative subparts

[John Griessen <john@xxxxxxxxxxxxxx>]

Karl Hammar wrote:
> john@xxxxxxxxxxxxxx:
>> Karl Hammar wrote:
>>> Is there a way to organize alternative subparts in a project, e.g.
>>> a cpu-card for one user will have one kind a bus-connector and for 
>>> another user another bus-connector, but still maintanable as one 
>>> project?
>> I would use the method where project definition is by separate directories
>> with different gafrc files containing different lists of libraries.
> 
> I don't understand this method, what is the reason for not sharing 
> libraries?

I was assuming 2nd user was new to everything and not part of your same company,
2 customers and maybe 2 design engineers in one company sounds like a better match
to what you are asking for.

> 
> For what I understand, a library is a good thing when sharing things,
> why should I want to use duplicate libraries when most of the design
> is common?
Only so selecting one or the other library changes the parts available.
If you have no name clashes, there's no need to have a subpart library.
> 
> Also, I want to share as much as possible, just e.g. be able to have
> a subpart where difference are between users.

> Cannot a new sybol be placed in a shared lib without conflict?

Sure. No problem. With a new name.

Like John Doty said, I like using a version control system using branches to freeze state of your libraries
for a product.  When you make a new one, you can copy just the schematic to start and reference
the current libraries to get improvements you've put in them and resolve any conflicts at the starting
phase of a design.  Using the version control branch for the product keeps you safe from
conflicts with new library parts of same name  not matching the earlier design -- that lets you
retest and analyze the earlier design just as it was.

Using version control branches is fine for two offshoots of a design at the same time too.
You ultimately want an unchanging snapshot of them to make more batches from.  If you
check out a new branch, it looks like a copy of the state of your libraries, then you add some new,
and you don't see that in the main branch, and maybe someone added part to libraries in it
while working on the similar version of a product for customer 2.  You can do a git merge to
the libraries and look at any differences and OK it to merge them in when you see only
new parts added and no name clashes.   Just like for code.

I've been doing some free published code for hardware modules so the version control is
separate and I can't version control the hardware and software at the same go, but I
like that idea John D. uses.

John Griessen

-- 
Ecosensory   Austin TX


_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user