RE: Copy command copies directories I don't want

[Tim Nelson]

On Thu, 25 Aug 2005, Ed Brown wrote:

> > 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?
>
> 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?
>
> 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).

	He's adding stuff to the end of the filename.  So, for example, 
say we want file foo on servers that are both mail servers and web 
servers, we get this:

Mark (msa) solution:
.../usr/local/bin/foo.__MailServer.WebServer__

Tim templating solution:
.../MailServer.WebServer/usr/local/bin/foo

	Naturally I like mine better, but his solution should work just as 
well if that's the way he wanted to do it (unless I've missed something). 
The disadvantage to his way is, he'd have to modify the templating code to 
get it to do that, instead of just downloading and using it.

	The only problem with his is if he ever wants a file that's 
actually named t.__class__ and it strips the stuff off the end.

	But now he knows why I like "find . -name 'foo*'" and that sort of 
thing.

        :)

--
Kind Regards,
 
Tim Nelson
Server Administrator
 
P: 03 9934 0888
F: 03 9934 0899
E: tim.nelson@webalive.biz
W: www.webalive.biz
 
WebAlive Technologies
Level 1, Innovation Building
Digital Harbour
1010 La Trobe Street
Docklands Melbourne VIC 3008

This email (including all attachments) is intended solely for the named 
addressee. It is confidential and may contain legally privileged information. If
you receive it in error, please let us know by reply email, delete it from your 
system and destroy any copies. This email is also subject to copyright. No
part of it should be reproduced, adapted or transmitted without the written 
consent of the copyright owner.

Emails may be interfered with, may contain computer viruses or other defects 
and may not be successfully replicated on other systems. We give no
warranties in relation to these matters. If you have any doubts about the 
authenticity of an email purportedly sent by us, please contact us immediately.