[Portableaserve-discuss] Changing paserve's system name to paserve to make way for original aserve in Quicklisp (was: Re: ipv6 support for portableaserve)

[Dave C. <dav...@ge...>]

Dear Rudi, portableaserve maintainers & users,



> In general, I’m all in favor of using common (and maintained) portable
> libraries and removing as much stuff from acl-compat as possible.  :)



A new compatibility layer, "zacl," has been developed which can play a
similar role to acl-compat, and is targeted toward current "original"
AllegroServe (1.3.42):

  https://gitlab.common-lisp.net/zbeane/zacl

zacl has initially targeted CCL, and it has been tested (albeit lightly)
CCL. An effort to port to other CLs is ongoing.

For purposes of allowing zacl, original AllegroServe, and
portableallegroserve all to co-exist in Quicklisp, would you guys mind
changing the system name in portableallegroserve from "aserve" to "paserve"
?  Zacl is currently working with a very lightly tweaked current version of
aserve (details in the README of the above gitlab project). The idea is to
minimize (ideally completely eliminate) any need for changes to original
aserve and have it work with zacl.

So for all this to work smoothly within Quicklisp, Quicklisp will have to
start carrying a mirror as close as possible (or identical) to original
aserve, and that means claiming back the system name "aserve."  (I know it
wasn't in Quicklisp first, but it was published with the asdf system name
"aserve" first).

At the risk of being presumptuous, I've attached a patch which effects this
change.


-- 
My Best,

Dave Cooper, david.cooper@gen.works
genworks.com, gendl.org
+1 248-330-2979