Re: [SSI-devel] Re: RFC: Restructuring the trunk and Debian code

[Aneesh K. KV <ane...@di...>]

Watson, Brian J. (HP) wrote:

>Aneesh Kumar KV wrote:
>  
>
>>I will say the trunk should include all the openssi codes ( That we 
>>developed ) for both redhat and debian  if at all there is a
>>    
>>
>dependency 
>  
>
>>on distribution. We can write makefiles to make sure right files are 
>>picked during a build. This will be the openssi project releasesd 
>>source.
>>    
>>
>
>I have no problem with rolling different source releases for Red Hat and
>
>Debian. Because the base code is so dramatically different (particularly
>
>in the kernel), it's an exercise in futility to create a source release 
>that works for both.
>
>Note that the source release I've been using lately for Red Hat is just 
>a tarball of SRPMs. I'm not sure this is even useful to anybody. 
>Developers and bleeding edge users should be using CVS.
>
>  
>
>>I am not sure whether COMMON will include all these. For example 
>>ssi_distro.pm for redhat and debian . Are they tagged COMMON ?  What i
>>    
>>
>
>  
>
>>was looking at is one code base released by openssi project that will 
>>build on both redhat and debian.
>>    
>>
>
>I've had a policy of making all cluster-tools and openssi-tools files 
>COMMON. This includes ssi_distro.pm, ssi_arch.pm, etc. I'm comfortable 
>with these packages sharing common source between Debian and Red Hat, 
>since they were entirely written by us. They're not based on any source 
>code that might be different between Debian and Red Hat.
>
>If you want to see the files that are marked COMMON, do a CVS checkout 
>of ci and openssi with this tag.
>
>  
>
>>The rest of the utlities like e2fsprogs  util-linux etc will be merged
>>    
>>
>
>  
>
>>over a period of time to their base code in either redhat or debian  
>>distro.
>>    
>>
>
>I'm not sure I understand what you mean. The RH version of these 
>utilities have already been merged with the OpenSSI code.
>  
>

Ok i was wondering we are going to have different branches for 
openssi-tools and cluster-tools also.  But your explanation above made 
it clear

We will have debian and redhat branches  for
1) kernel
2) e2fsprogs
3) util-linux
4) devfsd
5) sysvinit
6) initrd-tools

The rest will all be common code . Right ?


-aneesh

-- 
ph: 603-884-5742