[ECOS] the ecos/packages/hal/common is missing for ecos-arm cvs alias module

[ECOS] the ecos/packages/hal/common is missing for ecos-arm cvs alias module

[Bronislav Gabrhelik]

Hi all,

I am not sure if it is not bug in cvs client for windows platform, but
when I check out ecos-arm cvs module the ecos/packages/hal/common and
ecos/packages/hal/arm directories are empty. I tried both to me
available versions : the cygwin's cvs and  cvsnt. It seems to me like
!ecos/packages/hal has bigger preference. I develop only for Arm so I
would like to minimize the amount of source files to maintain.

What is the common practice? Should I use different module? Is it
somewhere documented?

Thanks in advance.
-bg

Below is what shows cvs co -c for ecos-arm module

sh-3.2$ cvs -d :pserver:anoncvs@ecos.sourceware.org:/cvs/ecos co -c

ecos-arm     -a ecos/packages/hal/common ecos/packages/hal/arm
             !ecos/packages/hal no-i386-devs no-mips-devs no-mn10300-devs
             no-powerpc-devs no-sh-devs no-sparclite-devs no-v85x-devs
             ecos-target-all

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] the ecos/packages/hal/common is missing for ecos-arm cvs alias module

[Andrew Lunn]

On Sun, Nov 18, 2007 at 10:43:51PM +0100, Bronislav Gabrhelik wrote:
> Hi all,
> 
> I am not sure if it is not bug in cvs client for windows platform, but
> when I check out ecos-arm cvs module the ecos/packages/hal/common and
> ecos/packages/hal/arm directories are empty. I tried both to me
> available versions : the cygwin's cvs and  cvsnt. It seems to me like
> !ecos/packages/hal has bigger preference. I develop only for Arm so I
> would like to minimize the amount of source files to maintain.

We have never allowed partial checkouts. You need to get everything.
at least to start with. Once you have everything checked out, you
could then in theory delete parts you don't need. Remember to also
edit your ecos.db file to remove packages you delete.
 
> What is the common practice? Should I use different module? Is it
> somewhere documented?

Using anoncvs is documented at:

http://ecos.sourceware.org/anoncvs.html

        Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Re: [ECOS] the ecos/packages/hal/common is missing for ecos-arm cvs alias module

[Bronislav Gabrhelik]

Andrew,

thanks for the response. I such case is more convenient for me to use
whole ecos module, so I can easier synchronize with ecos repository in
the future.

Thanks
-bg

On 11/18/07, Andrew Lunn <andrew@lunn.ch> wrote:
> On Sun, Nov 18, 2007 at 10:43:51PM +0100, Bronislav Gabrhelik wrote:
> > Hi all,
> >
> > I am not sure if it is not bug in cvs client for windows platform, but
> > when I check out ecos-arm cvs module the ecos/packages/hal/common and
> > ecos/packages/hal/arm directories are empty. I tried both to me
> > available versions : the cygwin's cvs and  cvsnt. It seems to me like
> > !ecos/packages/hal has bigger preference. I develop only for Arm so I
> > would like to minimize the amount of source files to maintain.
>
> We have never allowed partial checkouts. You need to get everything.
> at least to start with. Once you have everything checked out, you
> could then in theory delete parts you don't need. Remember to also
> edit your ecos.db file to remove packages you delete.
>
> > What is the common practice? Should I use different module? Is it
> > somewhere documented?
>
> Using anoncvs is documented at:
>
> http://ecos.sourceware.org/anoncvs.html
>
>        Andrew
>

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss