[M3devel] archive bloat

[Mika Nystrom]

Woudln't not including libm3back.a (e.g.) be a special case?

What if I write another program, call it "cm4", that imports the
m3back package... what does it link against?

    Mika

Jay writes:
>
>> These are surely needed for shipping.
>
>They are not.
>shipping doesn't require shipping dependencies. Only building does. And buildi
>ng has already occured.
>Shipping cm3 doesn't do much anyway. It ships the man page, ok. And it ships t
>he binary to a place other than where it is used, because cm3 is special.
> 
>I checked, the following works:
> 
> I already have a full enough package store.
> cd m3-sys/cm3
> cm3 
> cm3 -ship 
> rm -rf /cm3/pkg/m3front /cm3/pkg/middle /cm3/pkg/m3quake 
> cm3 -ship 
> 
>> That's because the archives are simply pre-built workspace parts.
>
>Still...
> 
>What do we gain by shipping the non-source part of the workspace?
>People can do incremental builds?
>In the future, if the package build / install split is earlier, it could ease 
>cross packaging, but currently?
> 
> 
>Packaging the source with each architecture is wasteful, but it does address v
>ersion skew.
>The binaries come with matching source.
> 
> 
> - Jay
>
>
>----------------------------------------
>> Date: Fri, 26 Jun 2009 14:18:49 +0200
>> From: wagner at elegosoft.com
>> To: jay.krell at cornell.edu
>> CC: m3devel at elegosoft.com
>> Subject: Re: [M3devel] archive bloat
>>
>> Quoting Jay :
>>
>>>
>>> Olaf I think you should trim the archives more. They have lots of
>>> intermediate files used to build cm3cg, including the identical copy
>>> m3cgc1, various static libraries, etc.
>>
>> That's because the archives are simply pre-built workspace parts.
>>
>>> I also don't see the utility of the Modula-3 standalone libraries
>>> for which we include what they built into, e.g. libm3back.a,
>>> libm3objfile.a, libm3front.a, libm3quake.a.
>>
>> These are surely needed for shipping.
>>
>>> I'm also not sure what all the CVS files end up doing.
>>> Do the make a checkout go fast?
>>> But surely..they are slightly wrong?
>>
> It's the CVS meta information; we can prune that if necessary.
>>
>> A generic way to prune the bin-ws archives would be to remove
>> everything that's not relevant for shipping, i.e. contained in
>> .M3SHIP. I'll have a look at that later.
>>
>>> I realize now that the reason lzma didn't always help is because the
>>> archives contain system.tgz.
>>
>> Olaf
>> --
>> Olaf Wagner -- elego Software Solutions GmbH
>> Gustav-Meyer-Allee 25 / Gebäude 12, 13355 Berlin, Germany
>> phone: +49 30 23 45 86 96 mobile: +49 177 2345 869 fax: +49 30 23 45 86 95
>> http://www.elegosoft.com | Geschäftsführer: Olaf Wagner | Sitz: Berlin
>> Handelregister: Amtsgericht Charlottenburg HRB 77719 | USt-IdNr: DE163214194
>>