RE: Copy command copies directories I don't want

[Mark]

> If your idea is to put every file that you need copied to 
> your clients under one file-system-mirror directory tree and 
> use multiple copy statements that differ only in the 
> includes/excludes/filters, I've one word of advice: don't.  
> This is REALLY not scalable.  Besides the limitations of 
> those parameters that you've already fought with, what do you 
> do when you need two different versions of the same file?

So far I have on tree with all files.
If I have a file that has different versions I name them accordginly, for 
example:
ldap.conf.___class1___
ldap.conf.___class2___

And then either have a single copy-action for this file that renames it while 
it copies it (if I only need to copy one file anyway),
or I add a rename action that gets triggered by the copy action.
Like you said, there is no perfect solution. But I thought the advantage of 
doing it this way would be that I have all files and
even all different versions of the same file that end up in /etc (or for this 
matter any other destination folder) in one place, so
it is easier to maintain them...

Not sure if there is anyting like a "best-practise" for this. I just noticed 
that everytime I started doing subfolders and spreading
files over different places, I get lost very quickly... So I thought I'd try it 
this way...


> I don't think there's one way to organize your sources.  But 
> absolutely you will want a structure that reflects to some 
> degree classes that you have defined (or hard classes). 

Have you figured out your own way of handling this, or have you come across any 
documentation or experience reports for this?
I'm at a point where it is not too late to change things, but so far any 
alternative I have come up with seemed to have one problem
or the other.
But after this recent directory-problem, it seems like I have to change 
SOMETHING...

Thanks,

MARK