[PD] resources required by ossia & else (was Re: deken server error?)

[IOhannes m zmoelnig]

On 12/16/20 1:35 PM, Alexandre Torres Porres wrote:
> hey, been getting this error when trying to upload stuff, seems like
> there's a server error but only for uploading stuff,  i can download just
> fine.

that's because the server ran out of disk space.
the server is a virtual machine, so i doesn't really have ressources as 
your desktop.


the issue is mainly caused by two deken projects consuming excessive 
amounts of disk space: "else" and "ossia"


## ossia
the ossia package itself is small (~3MB per package), but the 
accompanying sources are huge (>100MB zipped).
this is because the source-package contains >300MB of 3rd party 
libraries required for building.
@antoine would it be possible to omit the 3rd party libraries from the 
Sources-package and replace them with a README that says how to obtain 
them (or a script that fetches them)?


## else
the problem here is that there is a lot of platform independent data 
(e.g. a 5+MB-file of of white noise; wtf?), duplicated across all 
package versions and all platforms.
a typical package of else is about 30MB (zipped).
this does not seem too much, but given that there are 10 different 
architectures supported by else (and each is shipped in a separate 
package) and your upload rate is >3 per month (for each package!), the 
numbers just sum up.

i accept that this is to a certain extend a problem with the deken 
infrastructure (namely: not being able to specify dependencies).

it's also due to my insisting that you do not remove releases from 
puredata.info.

but i think we need to do something about it.

@porres for the time being i would like to ask you to:
- remove the live-electronics-tutorial from the "else" distribution 
until you do a proper release.
- merge multiple architectures into a single package (e.g. you could 
have a package containing Darwin-amd64-32, Darwin-i386-32, 
Linux-amd64-32, Linux-i386-32, Linux-arm64-32 and Linux-armv8-32; and 
probably Windows-i386-32 and Windows-amd64-32 too, but i didn't test as 
the current uploads are broken)
this requires some changes in your build pipeline, as you would need to 
use arch-specific suffixes (e.g. `l_i386` for Linux-i386-32) rather than 
the generic OS-specific ones (`pd_linux` for all the Linux archs).
as there we currently don't have different suffixes for the various 
32bit arm variants, you would still need to package these separately)

as an immediate remedy, i would even like to ask you to remove old 
alpha-releases (and it breaks my heart to say that).

fgsatmt
IOhannes