[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#32769: Packaging Next browser (Common Lisp) [work in progress]
From: |
Andy Patterson |
Subject: |
bug#32769: Packaging Next browser (Common Lisp) [work in progress] |
Date: |
Mon, 15 Oct 2018 23:11:20 -0400 |
Hi Pierre,
On Mon, 15 Oct 2018 11:34:14 +0200
Pierre Neidhardt <address@hidden> wrote:
> Question: do we need both "out" and "lib" outputs?
> My understanding is that "lib" is useful when one wants to start the
> program from a REPL. Correct?
"out" will always depend on "lib" for programs. We want to build it
the same way as other systems so that all of the source for the
program remains inspect-able at run-time, even if it's just a
one-liner.
--
Andy
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], (continued)
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Andy Patterson, 2018/10/11
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Pierre Neidhardt, 2018/10/11
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Pierre Neidhardt, 2018/10/11
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Andy Patterson, 2018/10/12
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Pierre Neidhardt, 2018/10/12
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Andy Patterson, 2018/10/12
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Pierre Neidhardt, 2018/10/14
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Andy Patterson, 2018/10/15
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Pierre Neidhardt, 2018/10/15
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Pierre Neidhardt, 2018/10/15
- bug#32769: Packaging Next browser (Common Lisp) [work in progress],
Andy Patterson <=
- bug#32769: Packaging Next browser (Common Lisp) [work in progress], Pierre Neidhardt, 2018/10/19