Actions
Forum Thread Details
  • Replies 6 replies
  • Subscribers 181 subscribers
  • Views 710 views
  • Users 0 members are here
Related

embedding version control information in schematic and board

Former Member

hi all,

 

after I've finally upgraded to eagle 6, I'm now experimenting with

putting my eagle files under version control (subversion in my case).

 

One of subversions features is putting revision information into the

files by keyword expansion.

As eagle now uses XML formatted files this now works without problems.

 

Just put for instance "$URL:$" or "$Revision:$" into a text and

subversion will replace it with "$URL: ULP ulp-name ulp-parameters ..."

 

Both solution would solve my immediate needs.

 

 

What do you think?

--

 

Lorenz

 

Parents

  • If I understand you correctly, I would second this approach.

    I also think that in eagle a custom string for >SVN_VERSION would be helpful.

    Subversion can execute a post commit script automatically on commit. So it could keep the revision in a text file for Eagle to read.?

  • in reply to igalloway

    Iain Galloway wrote:

    If I understand you correctly, I would second this approach.

    I also think that in eagle a custom string for >SVN_VERSION would be

    helpful.

     

    the situation has been getting better in the meantime.

     

    subversion 1.8 (due in about 4 week) will have custom keyword

    expansion.

    With that it will be possible to get revision info without any

    overhead into eagle properties and texts.

     

    If anyone want's to play with it sooner, tortoisesvn nightlies (

    http://nightlybuilds.tortoisesvn.net/latest) already ship with the

    custom keyword capabilities.

     

     

    Subversion can execute a post commit script automatically on commit.

     

    Subversion itself only has server-side hooks (but you probably are

    talking about tortoisesvn and its client-side hook).

     

     

    So it could keep the revision in a text file for Eagle to read.?

     

    that would not help much. You still need a mechanism in eagle that

    could access that information without the eagle files getting

    modified.

    --

     

    Lorenz

     

Reply
  • in reply to igalloway

    Iain Galloway wrote:

    If I understand you correctly, I would second this approach.

    I also think that in eagle a custom string for >SVN_VERSION would be

    helpful.

     

    the situation has been getting better in the meantime.

     

    subversion 1.8 (due in about 4 week) will have custom keyword

    expansion.

    With that it will be possible to get revision info without any

    overhead into eagle properties and texts.

     

    If anyone want's to play with it sooner, tortoisesvn nightlies (

    http://nightlybuilds.tortoisesvn.net/latest) already ship with the

    custom keyword capabilities.

     

     

    Subversion can execute a post commit script automatically on commit.

     

    Subversion itself only has server-side hooks (but you probably are

    talking about tortoisesvn and its client-side hook).

     

     

    So it could keep the revision in a text file for Eagle to read.?

     

    that would not help much. You still need a mechanism in eagle that

    could access that information without the eagle files getting

    modified.

    --

     

    Lorenz

     

Children
No Data