1. Forum
  2. Usenet
  3. COMP.LANG.LISP

  • releasing a first quicklisp package

    From Wolfgang Agnes@21:1/5 to All on Tue Oct 22 12:49:54 2024
    I wrote a couple of Common Lisp packages, one very small and a larger
    one that contains procedures for an Internet service. How should I
    organize them to be in a quicklisp package? Should I make two quicklisp packages? (I'd say no---one is too small to matter as a package.)

    Is it okay for two packages to form a single quicklisp package? How do
    you guys decide such things?

    Also, the larger package is not quite a package---it's really just the
    set of procedures that I need for the service. It's not likely that
    someone would use these packages except to run the Internet service. In
    other words, I intend to use quicklisp as a way to easily install the
    software. Is that okay?

    My plan for the installation of the service is to write a program that
    invokes quicklisp to download the packages and then create all the files necessary to run the service in a certain installation directly. In
    other words, the sysadmin would install and have the service ready to
    run with a single command. The procedure that would do such preparation
    would be in the Common Lisp package that quicklisp will download and
    install.

    I'd appreciate hearing the best practices. Thanks!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ralph Schleicher@21:1/5 to Wolfgang Agnes on Thu Oct 31 11:43:35 2024
    Wolfgang Agnes <[email protected]> writes:

    My plan for the installation of the service is to write a program that invokes quicklisp to download the packages and then create all the files necessary to run the service in a certain installation directly. In
    other words, the sysadmin would install and have the service ready to
    run with a single command. The procedure that would do such preparation would be in the Common Lisp package that quicklisp will download and
    install.

    So you presume the target system has a properly configured Common
    Lisp system installed? If so, why don't you just ship the source
    code together with the installation script so that you do not have
    to download anything? Otherwise, ever though about shipping a
    pre-built standalone executable file instead?

    --
    Ralph

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Wolfgang Agnes@21:1/5 to Ralph Schleicher on Thu Oct 31 08:17:05 2024
    Ralph Schleicher <[email protected]> writes:

    Wolfgang Agnes <[email protected]> writes:

    My plan for the installation of the service is to write a program that
    invokes quicklisp to download the packages and then create all the files
    necessary to run the service in a certain installation directly. In
    other words, the sysadmin would install and have the service ready to
    run with a single command. The procedure that would do such preparation
    would be in the Common Lisp package that quicklisp will download and
    install.

    So you presume the target system has a properly configured Common
    Lisp system installed?

    Yes, I do.

    If so, why don't you just ship the source code together with the
    installation script so that you do not have to download anything?

    I could have people clone a git repository and then say "make install". Something like that is what you have in mind? I think that would work
    well. But I also want to release a quicklisp package because I
    primarily have Common Lisp developers in mind.

    Otherwise, ever though about shipping a pre-built standalone
    executable file instead?

    As a second step---once I have a homepage set up, for instance. I'd
    build executables for popular systems.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ralph Schleicher@21:1/5 to Wolfgang Agnes on Thu Oct 31 17:48:14 2024
    Wolfgang Agnes <[email protected]> writes:

    But I also want to release a quicklisp package because I
    primarily have Common Lisp developers in mind.

    Sorry, here I misinterpreted your original post. I thought you
    want to install an application on a production machine.

    --
    Ralph

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)