what's the strategy for managing mostly common code with a few pr oject specific files?

[HEILES,KATRINA (HP-Vancouver,ex1)]

I have a set of code that is used by several projects.  Most of the code is common,

but some are project specific/configuration files.  What's the best way to manage this?

I'm envisioning that each project will pull the common code from a labelled version of the trunk. 

Does it makes sense to have the project specific files specified differently in a modules file?

I'd like projects to be able to pull from the same label but still have the ability to have a few files

not come from that label.

 

thanks for any suggestions,

Katrina