On Apr 8, 2006, at 9:40 AM, stv wrote:
> I realized there's one other twist ... conditionally deploying entire
> files depending on the "branch" ... something not really suited to the
> #IFDEF situaion (unless you no-op the entire file content ...)
Create scripts to do the deployment, and then include them in
Subversion. Then when you want to do the deployment it's just a
matter of running the appropriate script to deploy only those files
that should be included.
-Bill
>
> On 4/8/06, stv <stvsmth@gmail.com> wrote:
>> Ahhh. Yeah, well, I'm new to PHP as well, so thanks for the tip :)
>> That'll work just fine for what I need now.
>>
>> I'm still curious as to how one would handle this in a less trivial
>> example? Say I'm a printer manufacturer, and we have a print utility.
>> I rebrand my printers with the rebranded software ... is this type of
>> thing generally handled in #IFDEF code, or via scm?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Apr 10 15:26:33 2006