RE: [Subclipse-dev] RE: subclipse and externals

Hi Mark,

> I do not recall receiving the patch. What did it do?

I attach the original email. I would have done an up to date patch, but
I'm having problems connecting to
http://subclipse.tigris.org/svn/subclipse .

> The case presented is odd. I have never heard of defining an external

> that way, Does svn even support that? If it does, then why wouldn't
it
> create valid intermediate wc folders? It also seems odd that the
location
> she is pointing to would not just have that same folder structure, in
> which case the svn:externals would just need to point at the root and
all
> subfolders would come down.

The externals were updated in 1.1 to be processed in order specifically
in order to support this case. However, to the intermediate directory
they appear as unversioned objects; it's only when you go up to the
directory where they are on the svn:externals property that they become
known again.

> Finally, they could just create the folder structure in their main
project
> and only add svn:externals definitions at the bottom level.
> Then it would work fine.

The reason we have to do it is because we provide a family of drivers
for multiple hardware platforms and operating systems. For simplicity
of deployment, we provide the source code for any given kit as a single
directory. However, this is made up as follows:

 - Wolfson - stuff which is included in all kits, including assorted
   subdirectories.
 - Wolfson\OS - OS abstraction layer for our code - selected depending
on
   which operating system the kit is targeted at.
 - Wolfson\Platform - hardware abstraction layer for our code - selected
   depending on which hardware platform the kit is targeted for.

This allows us to build up an assortment of different kits using
externals at the level above. For example:

Wolfson_WinCE_XScale has svn:externals
        Wolfson http://subversion/svn/repos/trunk/components/Core
        Wolfson/OS
http://subversion/svn/repos/trunk/components/OS/WinCE
        Wolfson/Platform
http://subversion/svn/repos/trunk/components/HW/XScale

Wolfson_Palm_XScale has
        Wolfson http://subversion/svn/repos/trunk/components/Core
        Wolfson/OS
http://subversion/svn/repos/trunk/components/OS/Palm
        Wolfson/Platform
http://subversion/svn/repos/trunk/components/HW/XScale

Wolfson_WinCE_i.MX21 has
        Wolfson http://subversion/svn/repos/trunk/components/Core
        Wolfson/OS
http://subversion/svn/repos/trunk/components/OS/WinCE
        Wolfson/Platform
http://subversion/svn/repos/trunk/components/HW/i.MX21

etc.

This way, adding a new platform or operating system just adds one bit of
code, rather than multiplying the number of bits of code.

We can't put the externals on Core, because what goes beneath it varies
depending on the kit.

Does this explain it a bit more clearly?

Cheers,

Ian Brockbank
Applications Software Team Leader
e: ian.brockbank@wolfsonmicro.com / apps@wolfsonmicro.com
scd: ian@scottishdance.net
t: +44 131 272 7145
f: +44 131 272 7001
  

> -----Original Message-----
> From: Mark Phippard [mailto:MarkP@softlanding.com]
> Sent: 19 August 2005 14:42
> To: dev@subclipse.tigris.org
> Subject: Re: [Subclipse-dev] RE: subclipse and externals
>
> "Ian Brockbank" <Ian.Brockbank@wolfsonmicro.com> wrote on 08/19/2005
> 04:24:31 AM:
>
> > Which version of Subclipse are you using? I submitted a patch to
> Subclipse a
> > while ago about this problem (which affects us too). I
> can't remember
> if I
> > see it in 0.9.32 (which was released after the patch), and
> I'm afraid I
> can't
> > check just ATM because I don't have access at present, but
> if you're on
> an
> > earlier version it's well worth upgrading. Note you will need to
> upgrade your
> > svn clients to 1.2.1 to work with 0.9.32.
>
> I do not recall receiving the patch. What did it do?
>
> The case presented is odd. I have never heard of defining an
> external
> that way, Does svn even support that? If it does, then why
> wouldn't it
> create valid intermediate wc folders? It also seems odd that
> the location
> she is pointing to would not just have that same folder structure, in
> which case the svn:externals would just need to point at the
> root and all
> subfolders would come down.
>
> Finally, they could just create the folder structure in their
> main project
> and only add svn:externals definitions at the bottom level.
> Then it would
> work fine.
>
> Mark
>
>
>
> ______________________________________________________________
> _______________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security
> Management Services powered by MessageLabs.
> ______________________________________________________________
> _______________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>
>
> ______________________________________________________________
> __________
> This email has been scanned for all viruses by the MessageLabs Email
> Security System.
> ______________________________________________________________
> __________
>

attached mail follows:

Hi All,

I've got externals set up to map in our OS and HW directories into our
main library. I.e. on drivers:

WDCL http://subversion/svn/trunk/WDCL/core
WDCL/OS http://subversion/svn/trunk/WDCL/OS/WinCE
WDCL/HW http://subversion/svn/trunk/WDCL/HW/XScale

This all worked fine until recently, when Subclipse stopped managing the
files in OS and HW. I've just tracked that down to an assumption in
StatusCacheManager.java - the assumption that a parent being unmanaged
in
a given directory meant the child was unmanaged, which in this case is
invalid.

I attach a patch which fixes this for me.

Cheers,

Ian Brockbank
Applications Software Team Leader
e: ian.brockbank@wolfsonmicro.com / apps@wolfsonmicro.com
scd: ian@scottishdance.net
t: +44 131 272 7145
f: +44 131 272 7001