[Clas_offline] status of /group/clas/builds

[Johann Goetz]

The reason for the cleanup really comes from the fact that there were
multiple copies of the exact same build (same source, same compiler for
example), plus several builds that are no longer used by anyone. Because it
is impossible to tell who is using what, this was the only sure-fire way to
see what was still needed. But really, I just wanted to clean all this up
because, if I am expected to maintain the standard build for 6 GeV CLAS,
then I will do it my way unless told differently (this is merely service
work after all and is not part of my main job mandate).

-- Johann <https://sites.google.com/site/theodoregoetz/>


On Wed, Nov 20, 2013 at 12:39 PM, Valery Kubarovsky <vpk at jlab.org> wrote:

> Dear Johann,
>
> What is the reason for cleaning up our repository?
> I don't think that we can estimate what we need to keep
> by the end of the Collaboration meting. Is it so urgent?
>
> Regards,
> Valery
>
>
>
> On Wed, Nov 20, 2013 at 10:42 AM, Johann Goetz <theodore.goetz at gmail.com>wrote:
>
>> Hi All,
>> Since there are no more 32bit machines in JLab's computing future, we
>> have decided to clean up and consolidate the many now useless builds in
>> /group/clas/builds. The three legacy builds (64bit, 32bit, and test3) will
>> remain until the end of the collaboration meeting, but everything will be
>> replaced by a single build. The environment can be set by sourcing one of
>> these two files.
>>
>> t/csh:
>> source /group/clas/builds/environment.csh
>>
>> bash:
>> source /group/clas/builds/environment.sh
>>
>>
>> -- Johann Goetz, Dennis Weygand, Will Phelps
>>
>> _______________________________________________
>> Clas_offline mailing list
>> Clas_offline at jlab.org
>> https://mailman.jlab.org/mailman/listinfo/clas_offline
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mailman.jlab.org/pipermail/clas_offline/attachments/20131120/96e968eb/attachment-0001.html