{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Shon Vaughan <[EMAIL PROTECTED]>
Jason,
Thank you for the expert assistance.
I was using Project Builder and it was unable to correctly update despite
several attempt to update. Your Terminal command did what PB can't.
Hopefully, Apple will fix PB so that it works correctly with CVS.
It's possible now to make an Applescript that executes Terminal commands so
I'm going to figure out how to make one so that I can bypass this problem
with PB.
On 2/8/02 12:30 AM, "Jason Townsend" <[EMAIL PROTECTED]> wrote:
> on 2/7/02 11:38 PM, Shon Vaughan <[EMAIL PROTECTED]> wrote:
>> Is it *possible* to get CVC to update to a buildable version of Fire?
>>
>> *Every* time I update a valid Fire source folder via CVS there are missing
>> files and loads of errors because of those missing files. The only
>> workaround so far is to download the entire source each time I want to try
>> the latest build. It irks me because wasn't CVC created to avoid such a
>> wasteful download?
>>
>> Is there a trick to getting CVC to actually work that I've been missing?
>
> I usually do
>
> % cvs -q update -d
>
> In Terminal from inside the fire directory to get the latest sources. -d
> makes sure you get new directories.
>
> Are you trying to update from Project Builder? If so, I would suggest doing
> the update twice since I don't think it will update files it doesn't know
> about. The first update gets the latest project and the second gets the new
> files. If that fails, go to the Terminal and update before starting over
> from scratch.
>
> -Jason
Shon Vaughan <mailto:[EMAIL PROTECTED]>
Graphic Design and Web Site Development
_ _ _ _ _ _ _ _
to be yourself in a world that tries night and day to make you just like
everybody else is to fight the greatest battle there ever is to fight and
never stop fighting
-- e. e. cummings
{#} ----------------------------------------------------+[ fire ]+---
