best-practice for organizing sparse/end-user-specific files in a repos?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

hi all,

i've a question abt best-practice repos organization of sparsely-populated 'machine-specific'
content.

no doubt not a unique issue ... but a 1st-time occurrence for me.

to explain:

say i've a repos of ~ 10000 files, org'd across a hierarchy of ~250 dirs.

the repos will eventually be checked out to a number of different boxes.

while the vast majority of the repos files are to be identical from machine to machine, some
small number, say ~ 1%, contain machine-specific content ... for example, a machine name or an
IP address. these files are somewhat randomly distributed across the repos structure.

QUESTION:

how best to organize the machine-specific files?

if they were all collected in a single dir, i'd simply treat machine-specific data as a separate
project/dir, labeled with a tag ... and each machine would just check out the 'shared' trunk,
and its "named" dir. nbd.

but when these machine-specific data are sparsely dispersed throughout the repos, how do i
differentiate?

thoughts/suggestions are much appreciated!

thx,

richard

- --

/"\
\ / ASCII Ribbon Campaign
 X against HTML email, vCards
/ \ & micro$oft attachments

[GPG] OpenMacNews at gmail dot com
fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (Darwin)

iEYEAREDAAYFAkOdH3gACgkQlffdvTZxCMa+HQCfYDFVbeA1ELSQgQS55fmLXbN3
+lUAmwU0HdWipTMEvcBqRNOPDQmjwgut
=dUdK
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Dec 12 10:59:21 2005