Hi Andreas,
Answers to your extremely important questions below.
On 08/18/2014 11:38 PM, Andreas Tille wrote:
Hi Ira,
On Mon, Aug 18, 2014 at 01:42:51PM -0700, Ira Kalet wrote:
I had the good fortune at a recent social event to meet an attorney
for one of the big multinational corporations
On 08/11/2014 08:03 AM, Ian Jackson wrote:
Steve M. Robbins writes (Re: Status of uw-prism packaging for Debian):
My guess is that the legality of distribution hinges on how the software is
represented. For example, [1] defines device as:
any article, instrument, apparatus or
Hi Andreas,
OK, no promises and no more whining about my health issues. I will get
started on SLIK and then see where we stand with Prism.
Ira
On 08/01/2014 01:52 AM, Andreas Tille wrote:
Hi Ira,
On Thu, Jul 31, 2014 at 11:15:49AM -0700, Ira Kalet wrote:
Right, so I will plan on getting
Hi Andreas,
See below, comments further on SLIK and Prism.
On 07/31/2014 12:13 AM, Andreas Tille wrote:
Hi Ira,
On Wed, Jul 30, 2014 at 10:08:27PM -0700, Ira Kalet wrote:
Thanks for the reference to the policy and other documents. I now
have a pretty good sense of what is involved.
1. I
Hi Andreas,
Thanks for your continued interest. I actually have some time and
energy to work on this now. Building an executable from source in
Common Lisp is very different from C or other compiled-only languages.
Make is not applicable. It will have Lisp implementation
dependencies, so
Hi Andreas,
On 07/30/2014 02:51 PM, Andreas Tille wrote:
Hi Ira,
On Wed, Jul 30, 2014 at 02:43:40PM -0700, Ira Kalet wrote:
Thanks for your continued interest. I actually have some time and
energy to work on this now. Building an executable from source in
Common Lisp is very different from
On 07/17/2011 02:08 AM, Karsten Hilbert wrote:
On Fri, Jul 15, 2011 at 01:46:54PM -0700, Ira Kalet wrote:
I guess just renaming every *.cl to *.lsp would be not a god idea, right?
If you did, the package would not compile with ACL for the same
reason...but it would work OK with CLISP
On 07/16/2011 05:36 AM, Andreas Tille wrote:
Just a wild guess without having any look into the code: What about
creating a separate build tree with symlinks with the extension we need?
Meta question: Isn't it a bug of CLISP if it does not work with the
extensions that are used by other
Comments below.
On 07/15/2011 11:09 AM, Thorsten Alteholz wrote:
On Thu, 14 Jul 2011, Ira Kalet wrote:
I'm responding to Thorsten's attempt to build Prism in CLISP. It has
been done, but at this point you have to really know more about Lisp.
Ok, so I will help as far as I can and hope
Informatics
Email: ika...@uw.edu
Web: http://www.radonc.washington.edu/ira-kalet/
---
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4e1fb72e.9070...@uw.edu
, Ira Kalet wrote:
Dear Andreas,
I was looking over some old emails and found this correspondence. In
the 7 years that have passed, I did some work to remove dependencies of
Prism on OpenGL and on any code whose provenance we did not know. Also
the web page has moved. The new link is
http
11 matches
Mail list logo
