Mark, it seems there is an issue with the output produced from VSS in the
History/Update list. If a file is added or removed, it is difficult to
ascertain where the file was added or removed to. You get a project name, but its not
a full path like an update, that looks like this:
Update file = DataShaper.sln
Update Directory = $/Gloria/Source/Production/Syngenta/Gloria/Deployment/DataShaper
Add file = DBTestFixture.cs
Add Directory = DB.TestCases
The occurs for a Remove. On my current project on which I did a bit of exploration,
it seems we have a bunch of projects all called the same
(DB.TestCases for example), which exist underneath different parent directories. In
this situation it is impossible to know which DB.TestCases had
the DBTestFixture.cs added.
It could be I have missed something, so I am not 100% discounting this method with
VSS. Even if VSS is the only tool that couldnt benefit from
discriminate file access, it is definitely worth considering for the other SCC tools.
Nick.
"Mark Griffiths" <[EMAIL PROTECTED]> wrote:
>
> I'm all for making Draco more flexible - and for not enforcing the 'super
> clean' build
> method on everyone. It really sounds like we want to have a cleaner separation
> between
> the polling, getting and building within Draco.
>
> Nick, you described an idea to take a list of modifications and perform a 'get'
> on each
> changed file. Speaking for CVS and SVN, this functionality is already
> implemented in "cvs
> update" and "svn update". I remember VSS had a "get latest version" command.
> Is there
> anything stopping us from using this command? Is the performance just as bad
> as a fresh
> checkout?
>
> I ask because I am thinking that IRepository could be updated to:
>
> public interface IRepository {
> void Login();
> void GetSource(string workingDirectory);
> void UpdateSource(string workingDirectory);
> Modification[] GetModifications(DateTime sinceDate);
> }
>
> And in the Draco configuration:
>
> <svn>
> <url>http://svn.repository.com/svn/trunk</url>
> <user>johndoe</user>
> <password>password</password>
> <!-- the next element is optional -->
> <workingDirectory>c:\draco\myproject</workingDirectory>
> </svn>
>
> Draco's logic would be as follows:
>
> - if working folder not specified, then create one in the temp directory
> (as current)
>
> - if working folder specified, but it does not exist, then do a
> GetSource()
>
> - if working folder specified and it exists, then do a UpdateSource()
>
> We could also have an attribute on <workingDirectory> called persistent.
> Setting this
> attribute to false will delete the workingDirectory after use.
>
> Mark
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
> Free Linux Tutorials. Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Draconet-users mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/draconet-users
>
nick robinson
site : http://www.fromconcept.co.uk
weblog : http://www.fromconcept.co.uk/weblog.aspx
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Draconet-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/draconet-users
