RE: storing helix in local cvs repository

"Eric Hyche" <[email protected]>
Newsgroups gmane.comp.multimedia.helix.devel
Organization RealNetworks, Inc.
Message-ID <002c01c8d0a7$d1d5e170$e58e17ac@EHYCHED620>
John,

I would think that the build system is pretty agnostic of 
which CVS repository it's getting things from as long 
as the proper AddMultiCVS, AddCVS, and AddBIFPath
definitions are made in the .buildrc file.

Best place for this question would be ribosome-dev.

Eric

=============================================
Eric Hyche ([email protected])
Technical Lead
RealNetworks, Inc.  

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On 
> Behalf Of John Stirling
> Sent: Monday, June 16, 2008 5:50 AM
> To: [email protected]
> Subject: [Helix-client-dev] storing helix in local cvs repository
> 
> Our current system for building helix is to checkout based on a 
> datestamp and then to apply some patches.
> 
> This has some problems:
> . takes a long time to check everything out from helix repository
> . creating the patch files take time
> . reliant on helix servers working
> 
> Ideally we'd like to import a helix snapshot into a local cvs 
> repository 
> and build from there.
> 
> We've tried that in the past but got stuck somewhere along the line 
> (can't remember where).
> 
> Is that sort of thing basically supported by the build system 
> ? If so, 
> can you give me some advice on how to make that happen.
> 
> John
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Helix-client-dev mailing list
> [email protected]
> http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev
> 


_______________________________________________
Helix-client-dev mailing list
[email protected]
http://lists.helixcommunity.org/mailman/listinfo/helix-client-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.