Re: Problems with modules

[Mark E. Hamilton]

Allen,

Fisher, Allen wrote:
> I've got a ton of custom modules set up. I think there's two things you
> have going on. First is that the module has the same name as another in
> the repository and the other is that your params are out of order. I
> always put my excludes last..
>
> Try changing this:
>
> > playground -a !playground/rtest playground
>
>
> To this:
>
> newPlayground -a playground !playground/rtest
>
> I have several modules set up just like the above and they work just
> fine.

Thanks. The pattern I used came from Cederqvist (C.1.4). It works fine 
except when the module name is the same as the top-level directory name; 
then the 'infinite loop' error occurs. I tried switching the order as 
you suggested and I get the same results; it throws an infinite loop 
when the module 'playground' has the same name as the top-level 
directory 'playground'

Our basic problem is that we want to check out the 'playground' module 
and have the resulting directory be named 'playground', but with 
specific sub-directories excluded. (We also want only a single top-level 
directory in the repository, which precludes simply moving the unwanted 
directories elsewhere.) Only alias modules support excluding 
sub-directories, but they don't support renaming.

The module combination I tried was an attempt to include both 
sub-directory exclusion and directory renaming in a single module name:

playground_full -d playground playground
playground -a !playground/rtest playground_full

It worked fine until we tried checking out something that didn't exist, 
at which point it checked out the entire top-level directory hierarchy 
when I expected that it would have reported an error.

--
----------------
Mark E. Hamilton
Orion International Technologies, Inc.
Sandia National Laboratory, NM.
505-844-7666