Initial commit
This commit is contained in:
commit
94532a4761
|
@ -0,0 +1,132 @@
|
|||
# ---> Node
|
||||
# Logs
|
||||
logs
|
||||
*.log
|
||||
npm-debug.log*
|
||||
yarn-debug.log*
|
||||
yarn-error.log*
|
||||
lerna-debug.log*
|
||||
.pnpm-debug.log*
|
||||
|
||||
# Diagnostic reports (https://nodejs.org/api/report.html)
|
||||
report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
|
||||
|
||||
# Runtime data
|
||||
pids
|
||||
*.pid
|
||||
*.seed
|
||||
*.pid.lock
|
||||
|
||||
# Directory for instrumented libs generated by jscoverage/JSCover
|
||||
lib-cov
|
||||
|
||||
# Coverage directory used by tools like istanbul
|
||||
coverage
|
||||
*.lcov
|
||||
|
||||
# nyc test coverage
|
||||
.nyc_output
|
||||
|
||||
# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
|
||||
.grunt
|
||||
|
||||
# Bower dependency directory (https://bower.io/)
|
||||
bower_components
|
||||
|
||||
# node-waf configuration
|
||||
.lock-wscript
|
||||
|
||||
# Compiled binary addons (https://nodejs.org/api/addons.html)
|
||||
build/Release
|
||||
|
||||
# Dependency directories
|
||||
node_modules/
|
||||
jspm_packages/
|
||||
|
||||
# Snowpack dependency directory (https://snowpack.dev/)
|
||||
web_modules/
|
||||
|
||||
# TypeScript cache
|
||||
*.tsbuildinfo
|
||||
|
||||
# Optional npm cache directory
|
||||
.npm
|
||||
|
||||
# Optional eslint cache
|
||||
.eslintcache
|
||||
|
||||
# Optional stylelint cache
|
||||
.stylelintcache
|
||||
|
||||
# Microbundle cache
|
||||
.rpt2_cache/
|
||||
.rts2_cache_cjs/
|
||||
.rts2_cache_es/
|
||||
.rts2_cache_umd/
|
||||
|
||||
# Optional REPL history
|
||||
.node_repl_history
|
||||
|
||||
# Output of 'npm pack'
|
||||
*.tgz
|
||||
|
||||
# Yarn Integrity file
|
||||
.yarn-integrity
|
||||
|
||||
# dotenv environment variable files
|
||||
.env
|
||||
.env.development.local
|
||||
.env.test.local
|
||||
.env.production.local
|
||||
.env.local
|
||||
|
||||
# parcel-bundler cache (https://parceljs.org/)
|
||||
.cache
|
||||
.parcel-cache
|
||||
|
||||
# Next.js build output
|
||||
.next
|
||||
out
|
||||
|
||||
# Nuxt.js build / generate output
|
||||
.nuxt
|
||||
dist
|
||||
|
||||
# Gatsby files
|
||||
.cache/
|
||||
# Comment in the public line in if your project uses Gatsby and not Next.js
|
||||
# https://nextjs.org/blog/next-9-1#public-directory-support
|
||||
# public
|
||||
|
||||
# vuepress build output
|
||||
.vuepress/dist
|
||||
|
||||
# vuepress v2.x temp and cache directory
|
||||
.temp
|
||||
.cache
|
||||
|
||||
# Docusaurus cache and generated files
|
||||
.docusaurus
|
||||
|
||||
# Serverless directories
|
||||
.serverless/
|
||||
|
||||
# FuseBox cache
|
||||
.fusebox/
|
||||
|
||||
# DynamoDB Local files
|
||||
.dynamodb/
|
||||
|
||||
# TernJS port file
|
||||
.tern-port
|
||||
|
||||
# Stores VSCode versions used for testing VSCode extensions
|
||||
.vscode-test
|
||||
|
||||
# yarn v2
|
||||
.yarn/cache
|
||||
.yarn/unplugged
|
||||
.yarn/build-state.yml
|
||||
.yarn/install-state.gz
|
||||
.pnp.*
|
||||
|
|
@ -0,0 +1,56 @@
|
|||
Preamble to the Gnu Lesser General Public License
|
||||
|
||||
Copyright (c) 2016 Franz Inc., Berkeley, CA 94704
|
||||
|
||||
The concept of the GNU Lesser General Public License version 2.1 ("LGPL")
|
||||
has been adopted to govern the use and distribution of above-mentioned
|
||||
application. However, the LGPL uses terminology that is more appropriate
|
||||
for a program written in C than one written in Lisp. Nevertheless, the
|
||||
LGPL can still be applied to a Lisp program if certain clarifications
|
||||
are made. This document details those clarifications. Accordingly, the
|
||||
license for the open-source Lisp applications consists of this document
|
||||
plus the LGPL. Wherever there is a conflict between this document and
|
||||
the LGPL, this document takes precedence over the LGPL.
|
||||
|
||||
A "Library" in Lisp is a collection of Lisp functions, data and foreign
|
||||
modules. The form of the Library can be Lisp source code (for processing
|
||||
by an interpreter) or object code (usually the result of compilation of
|
||||
source code or built with some other mechanisms). Foreign modules are
|
||||
object code in a form that can be linked into a Lisp executable. When
|
||||
we speak of functions we do so in the most general way to include, in
|
||||
addition, methods and unnamed functions. Lisp "data" is also a general
|
||||
term that includes the data structures resulting from defining Lisp
|
||||
classes. A Lisp application may include the same set of Lisp objects
|
||||
as does a Library, but this does not mean that the application is
|
||||
necessarily a "work based on the Library" it contains.
|
||||
|
||||
The Library consists of everything in the distribution file set before
|
||||
any modifications are made to the files. If any of the functions or
|
||||
classes in the Library are redefined in other files, then those
|
||||
redefinitions ARE considered a work based on the Library. If additional
|
||||
methods are added to generic functions in the Library, those additional
|
||||
methods are NOT considered a work based on the Library. If Library classes
|
||||
are subclassed, these subclasses are NOT considered a work based on the Library.
|
||||
If the Library is modified to explicitly call other functions that are neither
|
||||
part of Lisp itself nor an available add-on module to Lisp, then the functions
|
||||
called by the modified Library ARE considered a work based on the Library.
|
||||
The goal is to ensure that the Library will compile and run without getting
|
||||
undefined function errors.
|
||||
|
||||
It is permitted to add proprietary source code to the Library, but it must
|
||||
be done in a way such that the Library will still run without that proprietary
|
||||
code present. Section 5 of the LGPL distinguishes between the case of a
|
||||
library being dynamically linked at runtime and one being statically linked
|
||||
at build time. Section 5 of the LGPL states that the former results in an
|
||||
executable that is a "work that uses the Library." Section 5 of the LGPL
|
||||
states that the latter results in one that is a "derivative of the Library",
|
||||
which is therefore covered by the LGPL. Since Lisp only offers one choice,
|
||||
which is to link the Library into an executable at build time, we declare that,
|
||||
for the purpose applying the LGPL to the Library, an executable that results
|
||||
from linking a "work that uses the Library" with the Library is considered a
|
||||
"work that uses the Library" and is therefore NOT covered by the LGPL.
|
||||
|
||||
Because of this declaration, section 6 of LGPL is not applicable to the Library.
|
||||
However, in connection with each distribution of this executable, you must also
|
||||
deliver, in accordance with the terms and conditions of the LGPL, the source code
|
||||
of Library (or your derivative thereof) that is incorporated into this executable.
|
Loading…
Reference in New Issue