That's your opinion - and everyone is entitled to one :)

However, like the name SCM - Software Change Management - should
indicate, it should be all about controlling software that you can
change. In other words - software you have source for and can legally
change while abiding by it's license.

SCM shouldn't be about built artefacts - which is what a binary
executable or linked library is. Built artefacts are obtained from their
sources, who no doubt have appropriate SCM processes to control their
code. Their code - and by extension, their artefact - should never have
to be "managed" by you.

Gerard Fernandes

-----Original Message-----
From: Dave [mailto:[EMAIL PROTECTED] 
Sent: 04 June 2008 17:07
To: [email protected]
Subject: Using Ivy with Telelogic Synergy

Hey all,
I believe best practice SCM means keeping your library dependencies
under version control. I'm kind of disappointed to see what limited (is
there
any?) support Ivy has for SCM tools. I'm wondering in particular if any
has managed to integrate Ivy with library dependencies managed with
Telelogic Synergy. I've been looking at the IvySVN project (
http://www.audioscrobbler.net/development/ivysvn/)  for a little
inspiration, but would rather not have to port it to work with Synergy
if I can avoid it.

Any help/tips would be appreciated

Regards,
Dave

--
There are 10 types of people in the world.
Those who understand binary and those who do not.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 
- - - -

This message is intended only for the personal and confidential use of the 
designated recipient(s) named above.  If you are not the intended recipient of 
this message you are hereby notified that any review, dissemination, 
distribution or copying of this message is strictly prohibited.  This 
communication is for information purposes only and should not be regarded as an 
offer to sell or as a solicitation of an offer to buy any financial product, an 
official confirmation of any transaction, or as an official statement of Lehman 
Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  
Therefore, we do not represent that this information is complete or accurate 
and it should not be relied upon as such.  All information is subject to change 
without notice.



Reply via email to