Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C cl-smtp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • cl-smtp
  • cl-smtp
  • Issues
  • #2
Closed
Open
Issue created Oct 24, 2015 by Dave Cooper@dcooperContributor

tests.lisp depends on asdf

Hi,

As the subject indicates, test.lisp contains a reference to asdf:component-pathname. This makes it impossible to load a cl-smtp--all-systems fasl (as generated by (asdf:operate 'asdf:monolithic-compile-bundle-op :cl-smtp)) into an image which does not have asdf available.

As a possibly temporary workaround, i have commented "tests" out of the :components section of my cl-smtp.asd. But in general, tests probably don't need to be built-in by default into a production system. Perhaps the tests could be made into a static-file, or maybe broken out into their own :cl-smtp-tests system, and not compiled & loaded by default with the :cl-smtp system?

Regards,

Dave

Assignee
Assign to
Time tracking