<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2018-08-22 02:10 PM, Pascal
Bourguignon wrote:<br class="">
</div>
<blockquote type="cite"
cite="mid:A058658B-6F5D-4887-8AF5-AF236437DA4D@informatimago.com">
<div>
<blockquote type="cite" class="">
<div class="">On 22 Aug 2018, at 00:36, Daniel Pezely <<a
href="mailto:daniel@pezely.com" class=""
moz-do-not-send="true">daniel@pezely.com</a>> wrote:</div>
<div class="">
<meta http-equiv="content-type" content="text/html;
charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
<p class="">I posted this to Stack Overflow but was hoping
for more input.<br class="">
</p>
<p class=""><a class="moz-txt-link-freetext"
href="https://stackoverflow.com/questions/51638864/common-lisp-style-multiple-packages-in-same-repo"
moz-do-not-send="true">https://stackoverflow.com/questions/51638864/common-lisp-style-multiple-packages-in-same-repo</a></p>
<div class="post-text" itemprop="text">
<p class="">May I get recommendations or links to
representative code repositories with good style for
multiple related Common Lisp packages, please? [...]<br>
</p>
</div>
</div>
</div>
</blockquote>
</div>
</blockquote>
<blockquote type="cite"
cite="mid:A058658B-6F5D-4887-8AF5-AF236437DA4D@informatimago.com">You’re
asking about different things. </blockquote>
<blockquote type="cite"
cite="mid:A058658B-6F5D-4887-8AF5-AF236437DA4D@informatimago.com">[...]<br>
</blockquote>
<blockquote type="cite"
cite="mid:A058658B-6F5D-4887-8AF5-AF236437DA4D@informatimago.com">
<div class="">In short: it depends!</div>
</blockquote>
<br>
<br>
Thanks, Pascal!<br>
<br>
Yes, these are different-- yet intertwined as integral parts of a
whole.<br>
<br>
Regarding git repos: in this case, it's just one person. The source
code is small enough that it would be maintained by one person for
foreseeable future, including potential forks supplying missing
features that might be apparent to those familiar with conventional
mmap use cases.<br>
<br>
Regarding asdf systems versus packages: the hooks for invoking the
test harness (Prove), launches via asdf mechanisms. For practical
purposes, these are tightly coupled here.<br>
<br>
Regarding files: as much as I admire the Smalltalk model, my
pragmatic side tips the scales in favour of being confined to
conventional CL tools and approach, hence: asdf, uiop-posix, Prove
and accommodating possible future inclusion by Quicklisp.<br>
<br>
<br>
Oddly enough, I was expecting to drink from a fire hose of highly
opinionated yet qualified CL advice.<br>
<br>
By way of comparison, I just returned from Rust Conf in Portland,
Oregon/US, last week and was reminded that their `cargo` package
manager has "workspaces" [1]. It synchronizes dependencies of
multiple packages within a common directory tree. That satisfies
criteria described in the original post, apart from being for a
different language of course.<br>
<br>
(Unfortunately, I don't have time to contribute a Lispy equivalent
as the most recent start-up company didn't quite go as intended...
but I digress.)<br>
<br>
[1]
<a class="moz-txt-link-freetext" href="https://doc.rust-lang.org/book/second-edition/ch14-03-cargo-workspaces.html">https://doc.rust-lang.org/book/second-edition/ch14-03-cargo-workspaces.html</a><br>
<br>
<br>
Thanks again for all your recommendations and insights!<br>
<br>
-Daniel<br>
<br>
</body>
</html>