Jens Pall wrote:
Brad Fuller wrote:
Jens Pall wrote:
Hi
How can I use Squeak in a commercial closed source project (whole
image)?
Have you seen how to lock down?
http://wiki.squeak.org/squeak/518
Yes, I've seen bits and pieces of the lock down procedure but haven't
been able to successfully lock an image (haven't tried very hard
though).
There were msgs about a month or two back in the squeak-dev ML about the
lock down package not working correctly on 3.9. But, I think there were
workarounds. Check the archives.
This is a step inn the right direction but I'm a bit concerned
about upgrades. How would I ship an upgrade without sending the whole
image again? Can I somehow export the new/changed bytecode and import it
at the customer's site?
Can you not employ a similar procedure as squeaksource? Make your own
mini SqueakMap that points only to your repo?
Or put a friendly frontend to Monticello pointing to your repo only?
Maybe you could also send update alerts if the person is online to
remind them to update.
brad
_______________________________________________
Beginners mailing list
Beginners@lists.squeakfoundation.org
http://lists.squeakfoundation.org/mailman/listinfo/beginners
