distributing .beam files/upgrading client software

[Gaspar Chilingarov]

Bjorn Gustavsson wrote:
> beam_lib can be used to make changes to .beam files such as strip
> out the compiler options.
> 
> /Bjorn
> 

thanks .

what about distributing beam files to clients - should I implement my
own distribution protocol?


> Gaspar Chilingarov <nm@REDACTED> writes:
> 
>> Hi all!
>>
>> If this questions have documented answers - just please say what and
>> where to rtfm :)
>>
>> Are there any more-or-less standard way to distribute .beam files to
>> multiple hosts ? I'm mainly interested of some, say, autoupgrade
>> feature, which will allow upgrade user software without disturbing users
>> and when developer wishes and not when user upgrades.
>>
>> Beam files are quite small and can be easily downloaded to clients which
>> makes erlang perfect for such kind of tasks, IMHO - so users are not
>> forced to download large executable files every time.
>>
>> I do NOT speak about upgrading code - because I'm running non-critical
>> application , which clients may be restarted without any problems.
>>
>> Another issue which interests me is now to strip this options
>>  {compile,[{options,[export_all]},
>>            {version,"4.3.9"},
>>            {time,{2005,12,28,8,51,18}},
>>            {source,"/usr/home/nm/tmp/a.erl"}]
>>
>> from module and thus from module_info() output?
>> compiler.erl (or something near it) should be modified?
>>
>> Are there way to distribute gzipped beam files - as far I looked on zlib
>> driver - it have hooks to load gzipped files - but how the should be
>> created?
>>
>>
>> Thanks in advance.
>>
>> -- 
>> Gaspar Chilingarov
>>
>> System Administrator,
>> Network security consulting
>>
>> t +37491 419763 (mob)
>> i 63174784
>> e nm@REDACTED
>>
> 


-- 
Gaspar Chilingarov

System Administrator,
Network security consulting

t +37491 419763 (mob)
i 63174784
e nm@REDACTED