00mjk / qlot

A project-local library installer for Common Lisp

Qlot

Qlot (pronounced kyü-'lät, like culotte) is a project-local library installer using Quicklisp facility. This aims to be like Bundler of Ruby or Carton of Perl.

Warning: This software is still BETA quality. The APIs will be likely to change.

Usage

# "qlfile" of "myapp"
git clack https://github.com/fukamachi/clack.git
github datafly fukamachi/datafly :branch v0.7.x
ql log4cl 2014-03-17

$ cd /path/to/myapp

# Installing libraries project-locally.
$ qlot install

# Updating depending libraries of a project.
$ qlot update

# Updating specific libraries
$ qlot update --project mito

# Execute a command with a project-local Quicklisp
$ qlot exec ros -S . run
$ qlot exec clackup app.lisp

What Qlot is trying to solve

We have Quicklisp, the central library registry. It made installation of libraries damn easy.

However, what only you can specify is the month of distribution. Which means you have to use all libraries of the same moment and you cannot use a newer/older version of a library for your project.

"local-projects/" or ASDF configurations may be a solution to this problem, but there are a couple of problems.

1. They are not project-local. If you have multiple projects that use the different version of the same library, it would be a problem.

2. They are difficult to fix the version or to update them. If your project need to work on other than your machine, for instance on other people's machine or on servers, the version of depending libraries should be the same.

This is what Qlot is trying to solve.

Requirements

• ASDF 3.2 or above

Installation

via Quicklisp

(ql:quickload :qlot)

via Roswell

It also can be installed with Roswell.

$ ros install qlot

# Install the latest version from GitHub
$ ros install fukamachi/qlot

It's almost the same as using Quicklisp, except it also introduces a shell command "qlot".

$ which qlot
/Users/nitro_idiot/.roswell/bin/qlot
$ qlot
Usage: qlot COMMAND [ARGS..]

COMMANDS:
    install
        Installs libraries to './.qlot'.

    update
        Makes './.qlot' up-to-date and update 'qlfile.lock'.
        Possible to update specific projects with --project option.
        ex) qlot update --project mito

    add [project name]
    add [source] [project name] [arg1, arg2..]
        Add a new library to qlfile and trigger 'qlot install'.
        ex)
          $ qlot add mito       # Add 'ql mito'
          $ qlot add ql mito    # Same as the above
          $ qlot add ultralisp egao1980-cl-idna
          $ qlot add github datafly fukamachi/datafly

    run
        Starts REPL with the project local Quicklisp dists (Same as 'qlot exec ros run').

    exec [shell-args..]
        Invokes the following shell-command with the project local Quicklisp.

    bundle
        Bundles project dependencies to './.bundle-libs'.
        Load './.bundle-libs/bundle.lisp' to make them available.
        Read https://www.quicklisp.org/beta/bundles.html for the detail.

OPTIONS:
    --version
        Show the Qlot version
    --debug
        A flag to enable debug logging. (Only for 'install' or 'update')
    --no-deps
        Don't install dependencies of all systems from the current directory.
    --cache [directory]
        Keep intermediate files for fast reinstallation.

Tutorial

Adding "qlfile"

Put a file "qlfile" at the root of your project directory.

See qlfile syntax section to know how to write it.

Installation of libraries

You can install libraries into the project directory via:

$ qlot install

It creates .qlot/ directory in the project directory and a file qlfile.lock.

qlfile.lock is similar to qlfile except the library versions are qualified. This will ensure that other developers or your deployment environment use exactly the same versions of libraries you just installed.

Make sure you add qlfile and qlfile.lock to your version controlled repository and make the .qlot/ directory ignored.

$ echo .qlot/ >> .gitignore
$ git add qlfile qlfile.lock
$ git commit -m 'Start using Qlot.'

Updating the project-local Quicklisp

You can update the content of .qlot/ directory via:

$ qlot update

# Update a specific project
$ qlot update --project mito
$ qlot update --project mito,sxql

It will also overwrite qlfile.lock.

Commands

install

qlot install will install Quicklisp and libraries that declared in qlfile project-locally. qlfile.lock will be used with precedence if it exists.

$ qlot install
$ qlot install /path/to/myapp/qlfile

update

qlot update will update the project-local .qlot/ directory using qlfile.

$ qlot update

# Update a specific project
$ qlot update --project mito
$ qlot update --project mito,sxql

add

qlot add will add a line to qlfile and invoke qlot install internally. It's arguments are same as the qlfile syntax.

$ qlot add mito                               # ql mito
$ qlot add ql mito                            # ql mito (Same as the above)
$ qlot add ultralisp egao1980-cl-idna         # ultralisp egao1980-cl-idna
$ qlot add github datafly fukamachi/datafly   # github datafly fukamachi/datafly

exec

qlot exec does following:

• configures CL_SOURCE_REGISTRY environment variable by adding a current directory;
• adds Roswell's bin directory to the PATH environment variable;
• executes given command with arguments.

Here are few usefull commands:

• qlot exec ros emacs - starts Emacs for development. Inferior lisp will use only systems, installed by qlot install. If you want to use systems from directories other than current and ./.qlot/, then set CL_SOURCE_REGISTRY variable before starting qlot. This can be useful in case, if you have development versions of some systems, for example, in ~/common-lisp/ directory and want to use them during project development:

  CL_SOURCE_REGISTRY=~/common-lisp// qlot exec ros emacs
  

  Read more about CL_SOURCE_REGISTRY in asdf's documentation.

• qlot exec ros build some-app.ros - another command, useful, to build a binary from systems, fixed in qlfile and qlfile.lock. This way you can be sure that your builds are stable.

qlfile syntax

"qlfile" is a collection of Quicklisp dist declarations. Each line of that represents a dist.

<source> <project name> [arg1, arg2..]

Currently, <source> must be one of dist, ql, ultralisp, http, git or github.

ql

ql <project name> <version>
ql <project name>

ql source will download libraries from Quicklisp official dist.

If you want to use Clack in Quicklisp dist of January 13, 2014, qlfile would be like this.

ql clack 2014-01-13

ultralisp

ultralisp <project name> <version>
ultralisp <project name>

ultralisp is same as ql except downloading from Ultralisp.

http

http <project name> <url> [<file md5>]

http source will download a tarball.

http yason http://netzhansa.com/yason.tar.gz

git

git <project name> <repos url>
git <project name> <repos url> :ref <commit ref>
git <project name> <repos url> :branch <branch name>
git <project name> <repos url> :tag <tag name>

git source will download libraries from a public git repository.

git clack https://github.com/fukamachi/clack.git

You can also specify :ref, :branch or :tag.

git clack https://github.com/fukamachi/clack.git :branch develop
git datafly https://github.com/fukamachi/datafly.git :tag v0.7.4
git cl-dbi https://github.com/fukamachi/cl-dbi.git :ref 54928984e5756e92ba298aae51de8b95a6b0cf4b

Retrieving from private repository

Qlot doesn't authenticate itself, but retrieving from private repository can be done via git's SSH key authentication. Which means, if the current user can git clone, Qlot also would be possible to do it.

git myapp [email protected]:somewrite-adtech/myapp

github

github <project name> <repos>
github <project name> <repos> :ref <commit ref>
github <project name> <repos> :branch <branch name>
github <project name> <repos> :tag <tag name>

github source is similar to git, but it is specifically for GitHub. As it uses GitHub API and tarballs GitHub serves, it doesn't require "git" command.

github datafly fukamachi/datafly
github datafly fukamachi/datafly :branch develop

dist

dist <dist name> <distribution URL> [<dist version>]

dist allows to use a custom Quicklisp dist, like Ultralisp.

dist quicklisp http://beta.quicklisp.org/dist/quicklisp.txt
dist ultralisp http://dist.ultralisp.org/

Priorities of distributions

If multiple distributions provide the same library, lower one would take priority over higher ones.

Working with SLIME

SLIME is the most popular development environment in Common Lisp. However, its REPL always loads the global Quicklisp, not the project-local one.

Here's quick steps to start project-local REPL with SLIME:

1. Add the following function to init.el.

(defun slime-qlot-exec (directory)
  (interactive (list (read-directory-name "Project directory: ")))
  (slime-start :program "qlot"
               :program-args '("exec" "ros" "-S" "." "run")
               :directory directory
               :name 'qlot
               :env (list (concat "PATH=" (mapconcat 'identity exec-path ":")))))

2. Relaunch the Emacs.
3. Invoke M-x slime-qlot-exec RET /path/to/project/.

Working with local git repositories

PROJECT_ROOT/.qlot/local-projects can be used for local git repositories. Symbolic links are also be accessible in Qlot environment.

Author

• Eitaro Fukamachi ([email protected])

Copyright

Copyright (c) 2014 Eitaro Fukamachi ([email protected])

License

Licensed under the MIT License.