RE: Copy command copies directories I don't want

[Mark]

One copy action per file really doesn't seem very scalable... I know, it would 
only be a last-resort fix, but still...

And splitting up the files into all kinds of different subdirectories is 
probably not scalable either. 
Are you actually using this approach? It seems to me like uou will end up with 
a new branch for each class combination/permutation
and figuring out what is where and whether all the files are where the belong 
will be a pain... Or am I wrong?

Thanks,

MARK

> -----Original Message-----
> From: Ed Brown [mailto:ebrown@lanl.gov] 
> Sent: Wednesday, August 24, 2005 3:39 PM
> To: Mark
> Cc: help-cfengine@gnu.org
> Subject: RE: Copy command copies directories I don't want
> 
> 
> On Wed, 2005-08-24 at 15:15, Mark wrote:
> 
> > I though I'd just keep a tree with all the files I need for the 
> > various copy actions for my different classes and then for 
> each copy 
> > action, I use an include list with the filenames I need. 
> But I guess it doesn't work that way... How else am I 
> supposed to do this???
> 
> When the includes/excludes/ignores/filters get unmanageable 
> or aren't working, maybe a simpler approach would suffice.  
> You aren't talking about very many files (at least you 
> haven't here), why not just use a copy statement for each 
> file, grouped by classes: very easy, very clear, not much 
> work for the very few files you've mentioned so far anyway. 
> Has the advantage of being able to individually specify 
> destination modes and ownership.
> 
> If you really want to use one copy statement per class, then 
> use different source directories.  That makes more sense to 
> me organizationally anyway.
> 
> copy:
>      $(config_download_dir)/etc_common/ ....
>   Special::
>      $(config_download_dir)/etc_special/ ....
> 
> -Ed
> 
> 
>