[Openroad-users] Subversion to track component changes

Fri May 18 01:12:45 EST 2007

Neil,

I can confirm that editing the components exports will almost certainly
cause problems immediately.

-Joe

________________________________

From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of
Neil.Warnock at luminary.co.uk
Sent: Thursday, May 17, 2007 7:54 AM
To: openroad-users at peerlessit.com
Subject: Re: [Openroad-users] Subversion to track component changes

Good news. Diffs works pretty well without any effort, particularly when
it's just the script that differs. I haven't risked merging - maybe it
will be ok but direct editing of the component in this manner could be a
bit hairy - there might magic numbers in the headers or something
similar that cause problems immediately or further downstream.

Will send diag directly. 

Neil Warnock 
Luminary Solutions 
Tel: +44 (0)845 371 4090 
Mob: +44 (0)771 265 0291  
Email: Neil.Warnock at luminary.co.uk 

For more information on Luminary go to http://www.luminary.co.uk
<http://www.luminary.co.uk/>  
Luminary Solutions Limited Registered in England No 4854134 VAT Reg No.
829 3166 13 
Registered Office: 16/17 Pavilion Business Park, Royds Hall Road, Leeds
LS12 6AJ 

________________________________

From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Pete
Rabjohns
Sent: 17 May 2007 15:22
To: International OpenROAD Users
Subject: Re: [Openroad-users] Subversion to track component changes

our developers are not allowed (well, not supposed) to touch the
official "build" catalogs at the moment - all code check in/check outs
are done by our home grown system - which also slaps an entry in
ii_locks for good measure. However, it has no support for branching
other than having a completely new copy of the component catalog - hence
the need to look for a simpler alternative.

My other issue with OpenROAD I think will be that the export file is not
maintainable by a difference/merge tool.

But I wonder whether we could generate our own 'extract' of the
component source into an XML/PlainText file using some kind of
serialisation mechanism... sounds scary but feasible. I should imagine
that extracting it out is one thing, but re-hydration of the object
could be a little tricky.

That way we could even use CVS/Subversion to do automatic merges for
us....

Of course when it's all OpenSource these are the kind of whizzo features
we'll be able to add... ;-)

Ps. any chance you could post that diagram to me separately please?

Pete

________________________________

From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of
Neil.Warnock at luminary.co.uk
Sent: 17 May 2007 13:26
To: openroad-users at peerlessit.com
Subject: Re: [Openroad-users] Subversion to track component changes

 (Diag removed. Too big. Sorry Paul.)

________________________________

From: Neil Warnock 
Sent: 17 May 2007 13:20
To: International OpenROAD Users
Subject: RE: [Openroad-users] Subversion to track component changes

Your plan should work well Pete. Another trick is to lock the components
in your OR repository that are not officially checked out (but are
required for compilation and browsing etc) by setting the 'locked_by'
att in the sys catalogues to a non-blank value such as "Subversion".
This prevents 'accidental' edits of not-checked-out-code. You'll get a
message from workbench along the lines of "This component is locked by
Subversion", a useful reminder in the middle of a hot, sweaty editing
session just before a deadline... :)  Using file based SCM systems such
as CVS or Subversion is useful where you have multiple releases,
multiple developers, loads of components and a mix of technologies,
scripts, installers etc.

Diagram of our as yet half-baked in-house affair attached.

Neil Warnock 
Luminary Solutions 
Tel: +44 (0)845 371 4090 
Mob: +44 (0)771 265 0291  
Email: Neil.Warnock at luminary.co.uk 

For more information on Luminary go to http://www.luminary.co.uk
<http://www.luminary.co.uk/>  
Luminary Solutions Limited Registered in England No 4854134 VAT Reg No.
829 3166 13 
Registered Office: 16/17 Pavilion Business Park, Royds Hall Road, Leeds
LS12 6AJ 

________________________________

From: openroad-users-bounces at peerlessit.com
[mailto:openroad-users-bounces at peerlessit.com] On Behalf Of Pete
Rabjohns
Sent: 14 May 2007 16:37
To: International OpenROAD Users
Subject: [Openroad-users] Subversion to track component changes

Hi Folks,

We've been using our own source control system for years, and I was
looking into replacing this with something like subversion.

Basically, the individual components would be stored in export files and
checked into the source control system.

Client side commands would be used to 'check out' 'check in' components
from/to the developers local catalog.

A build process would be written which extracts the current 'branch' of
source and copies each file into a component catalog, and then calls the
makeimage command line.

Before I investigate this any further, I was just looking for any
gotchas that other people may have come across or any useful tips.

The first one that comes to mind is preventing the SCCS from modifying
the export files in case of any 'conflicts', but I think this could
probably be configured to disable multiple check outs.

Pete

Pete Rabjohns

Technical Manager

Atex
Email: pete.rabjohns at atex.com <mailto:pete.rabjohns at atex.com>  
Web: http://www.atex.com <http://www.atex.com/> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://peerlessit.com/pipermail/openroad-users/attachments/20070517/8bc4c59a/attachment.html 