• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 263 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How do I stay current on 2.3.4 Rel 2.1 updates?

Ron Olson
Intellectual 680 points

There are times when I'd like to get current with improvements that are being made to 2.3.4 Rel 2.1.  On the other hand, I don't want to update to the current repository HEAD, only to find I've caught it in a buggy state.  Typically this would be handled by having the developers tag a reliable snapshot, and then the consumers could update to that tag.

So . . . what's the recommended procedure to safely get a new and safe snapshot from the repository?  Or, to be safe, do I need to wait for the next release?

Thanks,
Ron

  • 0
    TI__Expert 4390 points

    Hi Ron,

    For every release we create new manifest file, which has track of all commits for the release.

    For current release 2.1, the manifest file name is

    TI-Android-GingerBread-2.3.4-DevKit-2.1.xml

    One can always do repo sync with manifest file and get the snapshot of the release.

     

      $ repo init -u git://gitorious.org/rowboat/manifest.git -m TI-Android-GingerBread-2.3-DevKit-2.X.xml
  $ repo sync
    

    I hope this answer your query
    

    

    -
    

    satish
    

     
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    • 

		
	
  • 
		
    
			 


	
			
		
	









    
	
    
		
    
							
					
    
		
    
			
													0
							
			
				
									
							
						
				
			
			
			
					
    
	
    
	                                    
                      
    
                        
                          TI__Genius
                        10210 points
                      
    
                          
                   		
		
    
					
    We have two different kinds of Android manifests:
    

    a: Development manifest - This is of the format rowboat-<google android release name>.xml eg rowboat-froyo.xml or rowboat-gingerbread.xml and its arch-specific or dsp- variants
    

    b: DevKit Release manifest - This is of the format TI-Android-<google android release name and version>-DevKit-<TI Devkit release version>.xml e.g. TI-Android-GingerBread-2.3.4-DevKit-2.1.xml
    

    The development manifest always points to the HEAD version of the tree and may/may not be stable for your use case.
    The DevKit manifest points to a fixed state of the tree used by that particular release and stays constant irrespective of changes to the tree.
    

    If you wish to keep up with the latest development work you will need to use the development manifest. You can switch (or re-sync) to the DevKit release  version anytime using the following commands:
    

    $ cd rowboat
    $ repo init -u git://gitorious.org/rowboat/manifest.git -m <DevKit Release manifest>.xml
    $ repo sync
    

     
    
			
    

		
		
		
		
	
    
	
    
		
    
			
		
    
	
    

	            
                 	
	
    
				
		                
                
                
                
                
                
                
        		
		
				
    
			
		
    
		
		 
		
		
     
    
	
    

    
			
    
			
    
		
    

		
    
	
    •