[ts-general] Struggling to create.sql

Richard Pruss ricpruss at gmail.com
Thu Jun 30 01:36:16 EDT 2011


The git on github would be great. Then those like myself who do not feel up to contributing to the great depths of Bill's C++ can at contribute minor branches for things like the Makefile, the doc and minor bits like the API level in the test script etc.

I am clueless about the law, so excuse me if I am wrong but would GPLv3+ not stop companies from using the shim as if a company changed shim to do a trading system with it and made money they could be forced to publish their non-shim related code? 

The company I work for, by example (nothing to do with trading) has a blanket ban on any project using any GPLv3 code.

- Ric

On 30/06/2011, at 12:37 AM, R P Herrold wrote:

> On Wed, 29 Jun 2011, Richard Pruss wrote:
>> Russ, just a reminder to turn off -O3 in the Makefile to get the shim to work for MacOs.
> ughh -- that's a bug, but as I recall, it is one that is a conscious choice on Apple's side
> Just an update ... your post across the weekend caused me to revamp my testing build systems to follow some 'Agile' and TDD practices I have taken to using elsewhere.  I had simply not had the spare cycles to use them yet with the shim (as we are is a 'resting' phase as to the nest major featureset for the shim, and in 'bugfix' only mode. However, adding Makefile, or maybe even Cmake or autotools to address this build environment issue seems doable)
> Also, I've been frustrated not to have a public VCS for the project and was thinking of placing the initial tarball, and then each successive external tarball's diff into a 'git' repository, so a person could track the path we took to the first major version milestone.  Github seems the obvious choice for an external repository.  GPLv3+ license as to code, and CC-SA-3 for any documentation matter for those who choose to participate publicly
> So ... I saw the suggested reminder that we had see the script's issue with being run in the 'wrong' place, and it seemed to ring true to me ... SQL as a scripting language is woefully deficient (one can 'source' files, but has no ability to test where in a directory structure one is, nor to test return codes, and really needs to be wrapped up into a mediating wrapper containing such language elements)
> I remain hopeful of getting to this before the US Independence Day holiday, but, ...
> Best regards,
> -- Russ herrold

More information about the ts-general mailing list