Commit cdd5d110 authored by Francois-Rene Rideau's avatar Francois-Rene Rideau

Update debian packaging.

parent 4f4c7d03
......@@ -75,3 +75,37 @@ TODO for cl-launch as of 4.1.4
and a series of (declaim (optimize (speed 0) (size 0) (debug 0)
(compilation-speed 3))) and such to speed up the cl-launch
bootstrap?
* Fix debian packaging.
** Report by Tobias Frost <tobi@debian.org>
I see that your package has several DDs a uploaders. I'm wondering why
they don't upload it for you, if they co-maintain the package?
Did you file an RFS-Bug?
In d/changelog, there are many versions that where never in Debian,
also it reads more like an upstream changelog than an Debian changelog.
On the other side, changes to debian/* are not explained. (e.g the fact
and the resons why to update all the versions of the dependencies in
d/control). Refer to the Policy about d/changelog.
d/cl-launch.1 The manpage says "generated with Ronn/v0.7.3".
If it is autogenerated, it needs to be done at build time.
d/control
About your layout: It is not recommended to have the debian directory
in your master branch, as you cannot independently work on those.
Think of NMUs and how you would be able to integrate such changes in
your repository? (I suggest to put the debian packaging into its own
branch.)
This is also the point where I point people to
https://wiki.debian.org/UpstreamGuide, if they are upstream and
maintainer at the same time.
d/rules could be transformed to short debhelper format.
(note: did not check alls details in d/copyright, so just a few things
I saw at first glance)
d/copyright:
- The bugroff license text is missing.
- Copyright years are not up to date
......@@ -14,7 +14,7 @@ all: source
source:
@echo "Building Lisp source code for cl-launch in current directory"
@${CL_LAUNCH} --include ${PWD} -B install_path > /dev/null
@${CL_LAUNCH} --include "$${PWD}" -B install_path > /dev/null
install: install_binary install_source install_system install_cl
......@@ -22,26 +22,26 @@ install_binary: install_binary_standalone
install_source:
@echo "Installing Lisp source code for cl-launch in ${INSTALL_SOURCE}"
@mkdir -p ${INSTALL_SOURCE}/
@${CL_LAUNCH} --include ${INSTALL_SOURCE} -B install_path > /dev/null
@if [ ! $${PWD} = ${INSTALL_SOURCE} ] ; then \
@cp dispatch.lisp ${INSTALL_SOURCE}/ ; \
@mkdir -p "${INSTALL_SOURCE}/"
@${CL_LAUNCH} --include "${INSTALL_SOURCE}" -B install_path > /dev/null
@if [ ! "$${PWD}" = "${INSTALL_SOURCE}" ] ; then \
@cp dispatch.lisp "${INSTALL_SOURCE}/" ; \
fi
install_system: install_source
@echo "Linking .asd file for cl-launch into ${INSTALL_SYSTEMS}/"
@mkdir -p ${INSTALL_SYSTEMS}/
@if [ `dirname ${INSTALL_SYSTEMS}`/source/cl-launch = ${INSTALL_SOURCE} ] ; then \
ln -sf ../source/cl-launch/cl-launch.asd ${INSTALL_SYSTEMS}/ ; \
@mkdir -p "${INSTALL_SYSTEMS}/"
@if [ "`dirname '${INSTALL_SYSTEMS}'`/source/cl-launch" = "${INSTALL_SOURCE}" ] ; then \
ln -sf ../source/cl-launch/cl-launch.asd "${INSTALL_SYSTEMS}/" ; \
else \
ln -sf ${INSTALL_SOURCE}/cl-launch.asd ${INSTALL_SYSTEMS}/ ; \
ln -sf "${INSTALL_SOURCE}/cl-launch.asd" "${INSTALL_SYSTEMS}/" ; \
fi
install_binary_standalone:
@echo "Installing a standalone binary of cl-launch in ${INSTALL_BIN}/"
@sh ./cl-launch.sh --no-include --no-rc \
--lisp '$(LISPS)' \
--output ${INSTALL_BIN}/cl-launch -B install_bin > /dev/null
--output '${INSTALL_BIN}/cl-launch' -B install_bin > /dev/null
install-with-include: install_binary_with_include install_source install_system
......@@ -79,9 +79,9 @@ reinstall:
# This might fit your system, installing from same directory
reinstall_here:
-git clean -xfd
make install_source install_binary_standalone INSTALL_SOURCE=$$PWD INSTALL_BIN=$$PWD
make install_source install_binary_standalone INSTALL_SOURCE="$${PWD}" INSTALL_BIN="$${PWD}"
test:
tests:
./cl-launch.sh -l "${LISPS}" -B tests
WRONGFUL_TAGS := RELEASE upstream
......
usr/bin
usr/share/common-lisp/source/cl-launch
usr/share/doc/cl-launch
usr/share/man/man1
launcher.lisp wrapper.sh cl-launch.asd build.xcvb dispatch.lisp usr/share/common-lisp/source/cl-launch/
cl-launch usr/bin
debian/cl-launch.1
......@@ -5,8 +5,10 @@ Homepage: http://www.cliki.net/cl-launch
Maintainer: Francois-Rene Rideau <fare@tunes.org>
Uploaders: Christoph Egger <christoph@debian.org>, Kan-Ru Chen <koster@debian.org>, Milan Zamazal <pdm@debian.org>, Peter Van Eynde <pvaneynd@debian.org>, Julien Danjou <acid@debian.org>
Build-Depends: debhelper (>= 9)
Build-Depends-Indep: dh-lisp
Standards-Version: 3.9.6.1
Vcs-Git: https://gitlab.common-lisp.net/xcvb/cl-launch.git
Vcs-Browser: https://gitlab.common-lisp.net/xcvb/cl-launch
Package: cl-launch
Architecture: all
......
......@@ -86,3 +86,75 @@ License: LLGPL or Bugroff
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.
.
.
The "No problem Bugroff" license.
---------------------------------
.
Richard Stallman of the Free Software Foundation devised, in addition to
some marvelous software, the GNU General Public License (GPL for short).
Or the CopyLeft it is sometimes called.
.
It is quite a revolutionary document, using the "copyright" tool to to
protect your right to use free software.
.
Unfortunately using copyright to protect free software is a lot like using
a Jackal to guard the hens.
.
In fact, various inconveniences relating to this have resulted in
modifications such as the LGPL (Library General Public License) and more
recently the NPL (Netscape Public License)
.
I call these matters mere inconveniences, the real damage will occur when
the Jackal's, (sorry, I mean lawyers), actually get to test the GPL in
court for the first time.
.
Thus enter my version.
.
Its very simple.
.
Entirely consistent.
.
Completely unrestrictive.
.
Easy to apply.
.
The "No problem Bugroff" license is as follows...
.
The answer to any and every question relating to the copyright, patents,
legal issues of Bugroff licensed software is....
.
*Sure, No problem. Don't worry, be happy. Now bugger off.*
.
All portions of this license are important..
.
* "Sure, no problem." Gives you complete freedom. I mean it. Utterly
complete. A bit of a joke really. You have complete freedom anyway.
.
* "Don't worry, be happy." Apart from being good advice and a good song,
it also says :- No matter what anyone else says or does, you still have
complete freedom.
.
* Now bugger off. The only way to get rid of pushy Jackals is to ignore
them and not feed them. The GPL is just begging somebody to take it to
court. Can't you just see it. Exactly the same thing that happened when
some twit (not Linus) registered Linux as his own personal trademark.
People got upset, started a fund, and hired, off all ruddy things, a
Jackal to try and defend the chicken! Who really benefits from this
trademark / patent / copyright thing anyway? The lawyers. Who made it up
in the first place? The lawyers.
.
OK so the last part of the license sounds a bit harsh, but seriously
folks, if you are a :-
.
* Lawyer asking these legalese questions... You should go off and learn an
honest trade that will actually contribute to life instead of draining
it.
.
* Programmer asking these legalese questions... You have amazingly
powerful tools in your hands and mind, use them to ask and answer the
worthwhile questions of life, the universe and everything. Stop mucking
about with such legal nonsense and get back to programming.
.
* User/reader asking these question... Don't worry. Go off and be happy.
Have fun. Enjoy what has been created for you.
......@@ -10,6 +10,9 @@ include_dir := $(clc-source)/$(pkg)
doc-dir := usr/share/doc/$(debpkg)
%:
dh $@ --with lisp
configure: configure-stamp
configure-stamp:
dh_testdir
......@@ -23,10 +26,13 @@ build-indep: build-stamp
build-stamp: configure-stamp
dh_testdir
sh ./cl-launch.sh \
--include /${include_dir} \
--include "/${include_dir}" \
--lisp "sbcl ccl clisp abcl cmucl ecl mkcl allegro lispworks scl gcl xcl" \
--rc \
-B generate_install_files
# To generate the manpage from source, we could do this:
# sh ./cl-launch.sh -Ds cl-launch/release manpage
# But then we'd have to (1) package all the CL dependencies as .deb libraries (2) setup the source registry properly
touch build-stamp
clean:
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment