berry@stsci.EDU (Jim Berry) (08/01/88)
I've just written a patch editor to use with a KAWAI K1, and I'd like to
distribute it. It's free stuff (ok, well actually it's BEERWARE; if you
use it and like it and happen to see me somewhere you're supposed to buy
me a beer, and if that will never happen, you're supposed to buy somebody
else one and pretend it's me), but it uses Peter da Silva's STDFILE requester
and Bill Barton's midi.library code and I'm a little unsure about how
to distribute sources (binaries aren't a problem).
Would it be OK for me to distribute it with stdfile.lib (an object library
made from stdfile stdfile sources) and the stdfile POSTER (along
with a pointer where to find it)? It's a bit more of a problem with the
midi.library code because there is so much code involved, but the question
is the same.
I hate it when I get sources that I can't build because I'm missing a bunch
of support code.
I'm asking permission from you, Peter, to do the above (I'll call Bill
about it since he's a PLINK person and I'm not). But I'm also asking
in general what the deal is on this sort of thing.
Thanks.
PS - If anybody wants a copy of this code, send me mail. If you're not in
a hurry, though, I'm going to send it to the archives folks and you can get
it from there.
--
------------------------------------------------------------------------------
Jim Berry | UUCP:{arizona,decvax,hao}!noao!stsci!berry
Space Telescope Science Institute | ARPA: berry@stsci.edu
Baltimore, Md. 21218 | SPAM: SCIVAX::BERRY, KEPLER::BERRYpeter@sugar.uu.net (Peter da Silva) (08/01/88)
In article <383@stsci>, berry@stsci.EDU (Jim Berry) writes: > ...it uses Peter da Silva's STDFILE requester > and Bill Barton's midi.library code and I'm a little unsure about how > to distribute sources (binaries aren't a problem). I like the Beerware concept... make mine a Coopers Stout... You can distribute the sources any way you want. I'd rather you distributed the source rather than a library because that library might bite the big one when a new version of the compiler comes out (like, say, Manx 3.4->3.6). I'm posting this because this is a general problem... with two main compilers and different versions of same, objects just aren't that useful. Sigh. When you send the code to purdue, send me a copy. Purely for ego gratification. Karl might want to hack it into a DX7 editor, if he doesn't have one already. -- Peter da Silva `-_-' peter@sugar.uu.net Have you hugged U your wolf today?
berry@stsci.EDU (Jim Berry) (08/02/88)
From article <2381@sugar.uu.net>, by peter@sugar.uu.net (Peter da Silva): > > You can distribute the sources any way you want. I'd rather you distributed > the source rather than a library because that library might bite the big > one when a new version of the compiler comes out (like, say, Manx 3.4->3.6). Yeah, I sort of figured that too after I thought about it a bit (which was, of course, after I posted...). I probably won't distribute the STDFILE and midi.library sources, though (they'd make things kinda big). I'll just put 'here's where to find them' and 'I'll send them to you if you need them' stuff into the docs. > Peter da Silva `-_-' peter@sugar.uu.net > Have you hugged U your wolf today? -- ------------------------------------------------------------------------------ Jim Berry | UUCP:{arizona,decvax,hao}!noao!stsci!berry Space Telescope Science Institute | ARPA: berry@stsci.edu Baltimore, Md. 21218 | SPAM: SCIVAX::BERRY, KEPLER::BERRY