Windows XP and Junctions

[Mike Newsome <Mi...@hitekpower.com>]

Hello

I have a set of 'common files' used between (at present) 4 projects, and checked out via externals in each project.

When a new revision of the common code is being readied, I need to go round the 4 projects, updating the common code and checking correct operation. This leads to a lot of commits and updates.

I could simplify this by having one set of common code, and creating 'junctions' (symbolic links) to connect the normal experiences in.

Most tools are OK, but subversion doesn't like it. Update for example complains:
External        D:\MNewsome\WkSp\TetrodeMkII\FreeRTOS
External failed D:\MNewsome\WkSp\TetrodeMkII\FreeRTOS
Error           'D:\MNewsome\WkSp\TetrodeMkII\FreeRTOS' already exists and is not a directory

Also subWCrev returns '0'  for all the keywords I use ($WCREV$, $WCDATE$, $WCNOW$), and the null string for others ($WCURL$).

Is this expected? Or do I have some other problem?

Mike Newsome
Hitek Power Ltd, England


________________________________
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

Re: Windows XP and Junctions

[Ryan Schmidt <su...@ryandesign.com>]

On Jul 22, 2010, at 08:19, Mike Newsome wrote:

> I have a set of ‘common files’ used between (at present) 4 projects, and checked out via externals in each project.
>  
> When a new revision of the common code is being readied, I need to go round the 4 projects, updating the common code and checking correct operation. This leads to a lot of commits and updates.
>  
> I could simplify this by having one set of common code, and creating ‘junctions’ (symbolic links) to connect the normal experiences in.
>  
> Most tools are OK, but subversion doesn’t like it. Update for example complains:
> External        D:\MNewsome\WkSp\TetrodeMkII\FreeRTOS
> External failed D:\MNewsome\WkSp\TetrodeMkII\FreeRTOS
> Error           'D:\MNewsome\WkSp\TetrodeMkII\FreeRTOS' already exists and is not a directory
>  
> Also subWCrev returns ‘0’  for all the keywords I use ($WCREV$, $WCDATE$, $WCNOW$), and the null string for others ($WCURL$).
>  
> Is this expected? Or do I have some other problem?

AFAIK, Subversion (or rather the APR library it uses) does not support junctions.

RE: Windows XP and Junctions

[Mike Newsome <Mi...@hitekpower.com>]

Thanks Ryan, that confirms my thoughts (about junctions). I don't actually like them much!

David, I don't intend using junctions normally, just when I was making a comparatively large change, and wanted to test it on all four projects, without checking in, and updating then finding another gotcha in a project and doing the rounds this way.

Many thanks for your help.

Mike

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

Re: Windows XP and Junctions

[David Weintraub <qa...@gmail.com>]

You usually don't want to use links and junctions in your repository.
This usually causes more problems than it is worth.

Are you using the svn:external property? I'm not sure why you need to
go around and make changes in all of your projects. The whole point of
svn:external is to allow multiple projects to depend upon another set
of files in a controlled manner.

Most people link svn:externals to either a specific Subversion
revision or a particular Subversion tag. This way, the underlying code
isn't changed when a new revision of the external module is released.
Otherwise, you could have code that use to work suddenly fail and you
may not be able to easily do a rebuild.

But, there is no reason why you couldn't simply be using the latest
revision of the external project's files.

Another possibility is to create a branch for the external project
that the other four projects will use. When you are ready for release,
you can update that branch and the code will automatically be in the
other projects.

On Thu, Jul 22, 2010 at 9:19 AM, Mike Newsome
<Mi...@hitekpower.com> wrote:
> Hello
>
>
>
> I have a set of ‘common files’ used between (at present) 4 projects, and
> checked out via externals in each project.
>
>
>
> When a new revision of the common code is being readied, I need to go round
> the 4 projects, updating the common code and checking correct operation.
> This leads to a lot of commits and updates.
>
>
>
> I could simplify this by having one set of common code, and creating
> ‘junctions’ (symbolic links) to connect the normal experiences in.
>
>
>
> Most tools are OK, but subversion doesn’t like it. Update for example
> complains:
>
> External        D:\MNewsome\WkSp\TetrodeMkII\FreeRTOS
>
> External failed D:\MNewsome\WkSp\TetrodeMkII\FreeRTOS
>
> Error           'D:\MNewsome\WkSp\TetrodeMkII\FreeRTOS' already exists and
> is not a directory
>
>
>
> Also subWCrev returns ‘0’  for all the keywords I use ($WCREV$, $WCDATE$,
> $WCNOW$), and the null string for others ($WCURL$).
>
>
>
> Is this expected? Or do I have some other problem?
>
>
>
> Mike Newsome
>
> Hitek Power Ltd, England
>
>
>
> ________________________________
> This email and any files transmitted with it are confidential and intended
> solely for the use of the individual or entity to whom they are addressed.
> If you have received this email in error please notify the system manager.
> This message contains confidential information and is intended only for the
> individual named. If you are not the named addressee you should not
> disseminate, distribute or copy this e-mail.
>



-- 
David Weintraub
qazwart@gmail.com