Eagle projects cleanup and reorganisation

[Lothar Behrens]

Hi,

I have a question about reorganisation of eagle projects (or better
the complete eda projects).

There are many projects on different computers with propably many
copies (backup,old machines).

I want to pickup each project and put it into a version control system
and while this creating
a well organised directory structure. When doing this I am faced with
different versions of a project
named like thie:

205085.sch
205085.brd
205085a.sch
205085a.brd
205085b.sch
205085b.brd

Could these files renamed by a batch of by hand while sorted by date
(old files first) and then added to the version management system.

Is there any file indexing software, that is capable to collect file
date and put it into a database for
a better mechanism to clean up the old (wild) structure ?
(Propably with a filtering functionality to get all projects per
project number, but not the version after the numbers)

Thus I get this:

205085.sch (V1 in CVS for sample)
205085.brd (V1 in CVS for sample)
205085.sch (V2 in CVS for sample)
205085.brd (V2 in CVS for sample)
205085.sch (V3 in CVS for sample)
205085.brd (V3 in CVS for sample)

That way I could get rid of the many copies and the problem of a
backup issue.
Also I have a way to keep files per release in sync and have a central
backup mechanism
possible.

Thanks a lot,

Lothar

 

[James Morrison]

On Tue, 11 Nov 2008 03:50:24 -0500, Lothar Behrens wrote
(in article
<a9f390b0-d63d-41e8-9d21-0cf72bb0be01@e1g2000pra.googlegroups.com&gt:

Hi,

I have a question about reorganisation of eagle projects (or better
the complete eda projects).

There are many projects on different computers with propably many
copies (backup,old machines).

I want to pickup each project and put it into a version control system
and while this creating
a well organised directory structure. When doing this I am faced with
different versions of a project
named like thie:

205085.sch
205085.brd
205085a.sch
205085a.brd
205085b.sch
205085b.brd

Could these files renamed by a batch of by hand while sorted by date
(old files first) and then added to the version management system.

Is there any file indexing software, that is capable to collect file
date and put it into a database for
a better mechanism to clean up the old (wild) structure ?
(Propably with a filtering functionality to get all projects per
project number, but not the version after the numbers)

Thus I get this:

205085.sch (V1 in CVS for sample)
205085.brd (V1 in CVS for sample)
205085.sch (V2 in CVS for sample)
205085.brd (V2 in CVS for sample)
205085.sch (V3 in CVS for sample)
205085.brd (V3 in CVS for sample)

That way I could get rid of the many copies and the problem of a
backup issue.
Also I have a way to keep files per release in sync and have a central
backup mechanism
possible.

Hello Lothar,

We have 100's of EAGLE projects all checked into our version control system
(was CVS, migrated to subversion). I would highly recommend getting your
designs into a revision control for the reasons you highlighted.

Yes, the filename should not change between revisions so that you get the
maximum value out of revision control. So I think your general approach is a
good one.

Think about your directory structure too before you start--it can save a lot
of time in the future. Consider if you one or more general libraries and
also if you ever have project-specific libraries (we have that case for our
customers). Also consider throwing in design docs, source code, programmable
logic designs, .... A little thought up front can save tons of work later.

Good luck.

James.

------------------------------------------
 James Morrison  ~~~  Stratford Digital

 email:  sales@eaglecentral.ca
 fax:    888.701.8097
 web:    http://www.eaglecentral.ca

 Online EAGLE Dealer for US and Canada
 EAGLE Design Experts
 EAGLE Enterprise Toolkit
------------------------------------------

** Posted from http://www.teranews.com **