I apologize for being silent for a few days, I'm having my roof replaced
(in the snow!) and that has been more of an adventure than I would have
thought. So, it was really only my online self that was silent, I was
heating up the air outside with a few choice words.
I've messed around for about 5 minutes with the ability to export an
Eagle library into a script file (*.scr), and it is possible to get an
ASCII representation of everything in the library. It is also then
apparently possible to recreate the original library with that .scr
file. That said, the volume of data stored for the library is fairly
high, and moving any parts (or pieces of parts) creates a large amount
of changed data that hasn't really changed as much as the size of the
diff would indicate. It does seem to handle the addition of a part
reasonably well (the diff shows the added part), but I didn't try
deleting a part.
So, I would suggest that we could put both the library files and the
exported scripts under svn control so that a person could check out the
most current version of a library if they want to use it (the majority
of the users, I think) and people developing new gumstix related
libraries would be able to check and see when changes or additions were
made by looking at the exported script diffs. That would mean that
there would be two files needed for each revision of the library (since
one of the files is treated as a binary file it would be a bit wasteful,
I admit), but HDD space is cheap nowadays, right?
Another thing that I think might make things simpler for the tracking of
library things would be to keep several different libraries with only a
few parts in each one (hirose connectors in one, common power supply
components in another, connectors in yet another, etc). This might make
the binary repository bloat a little bit less painful as only the
(smaller) modified libraries would be checked in rather than one giant
library being checked in each time a small change was made to one component.
Dick Davies wrote:
>On 13/11/05, Dave Hylands <dhylands@...> wrote:
>>>Here's the set of challenges-- I really want to release them so we can
>>>all share edits. I strongly prefer SVN for version control; however,
>>>there is no diff for Eagle libraries or schematics because they're in
>>>Eagle's proprietary format. Since ulp and scr are text files, these are
>>So, even if you can't diff them, you could still put them under
>>version control. svn should be able to deal with binary files.
>It does (in its sleep) - the only problem is it has to do binary diffs to track
>revisions, so it bloats the repo a little. The locking mechanism is slightly
>different too, but that's a non-issue since I dont' suppose multiple users
>are going to be committing several versions of it a day...
>Knowing you have the latest version to hand would be worth that IMO.
>Rasputin :: Jack of All Trades - Master of Nuns
>SF.Net email is sponsored by:
>Tame your development challenges with Apache's Geronimo App Server. Download
>it for free - -and be entered to win a 42" plasma tv or your very own
>Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
>gumstix-users mailing list