[oi-dev] Release engineering // planing

[Alexander Pyhalov]

On 07/12/2013 19:52, Jim Klimov wrote:
> On 2013-07-12 17:42, Erol Zavidic wrote:
>> Important question over here:
>>
>> Are we ever going to promote hipster to /dev or /release then? This is
>> question in particular due to gcc/sunstudio differences.
>
> Why not? Code is code. /hipster can be compiled with GCC,
> which is an easier entry point for assorted contributors
> who did not get their hands on the one needed proprietary
> SunStudio version back in the day, and can't legally get
> it now, at least not for installation onto their PCs (may
> be it is legal to let them access a compile-farm with SS).
>
> Then when code is promoted to /dev and ultimately /release
> it can be recompiled with SS. On one hand it would give
> another tool's verification opinion about the code quality,
> and on another (if SS-built code so far is assumed more
> stable) - the less adventurous users would have more peace
> of mind with their non-experimental machines running /dev
> or /release.

Hello.

It's almost unreal. We now struggle with two different compilers in 
base, and the only logic way in my opinion is to just go on with GCC.
Code can't be "just recompiled", every Makefile needs its tweaks to 
support one or another compiler. If it is not tested with Sun Studio in 
/hipster, it will not work with Sun Studio in /dev and so it will 
require inadequate amount of energy to be ported.

Why do you need Sun Studio?
-- 
Best regards,
Alexander Pyhalov,
system administrator of Computer Center of Southern Federal University