What about writing some glue classes that check for the presence of the
libraries and download them automatically if the libraries are not present?
In this way, the developer would only have to specify a download url (or
at most one for each supported platform).
This sort of "caching" mechanism could be included in NativeBoost to
reduce the problem of hosting the libraries and would also reduce the
application size, since it would only download the binaries of the
current platform.
Tommaso
On 20/12/14 10:20, Ben Coman wrote:
Esteban Lorenzano wrote:
I don’t think so. We cannot pollute pharo file server with specific
libraries :(
we could in the future set up a service for that, but then we will
need to take into account licenses, etc. my recommendation is that
you do not include the library but instructions on where they can
download/build the proper libraries.
Esteban
On 19 Dec 2014, at 12:24, Blondeau Vincent
<[email protected]
<mailto:[email protected]>> wrote:
Hi,
Some of us are developing some applications by using NativeBoost,
which is a great tool for Pharo.
But when we want to distribute our application, we have to give the
libraries with it.
We can integrate the library in the package, give a link to download
an application and copy the libraries near the Pharo VM, or put it
on dropbox, but it seems that are not good solutions.
Maybe we should have a hosting platform for these libraries?
Does http://smalltalkhub.com <http://smalltalkhub.com/> or
http://files.pharo.org/ can do the hosting?
Cheers,
Vincent
This is an interesting question I might have to deal with some time,
so I had a look around for options. (As an aside, I came across this
interesting article "How I moved my websites to DropBox and Github"...
http://alexcican.com/post/guide-hosting-website-dropbox-github/ )
That makes me wonder what is wrong with using dropbox? You might use
it with a custom domain name so that later you can move services
transparently to users.
http://hostlater.com/2014/04/dropbox-custom-domain-name-url-2246/
Github recommends using either "Releases" or Amazon S3 & CloudFront.
Indeed it seems that "Releases" itself is built on top of CloudFront.
https://help.github.com/articles/distributing-large-binaries/
https://github.com/blog/1547-release-your-software
I followed this instruction as a trial...
https://help.github.com/articles/creating-releases/
and found it quite straightforward - see...
https://github.com/bencoman/Hello-World/releases
(I just used a jpg as an example)
cheers -ben
