Everywhere: Remove everything non-essential for "make clean all"

This commit removes everything not strictly necessary for running
"make clean all" inside jw-build.

packaging jw-devtest. This cuts the repo down from 24077 to 4725
lines of code.

The idea is to

1) Further remove bloat from the remaining bits

2) Re-add what's necessary to build and package other essential repos.

   The decision should be based on whether or not jw-build can also be
   useful in a non-janware context.

Signed-off-by: Jan Lindemann <jan@janware.com>
This commit is contained in:
Jan Lindemann 2025-11-14 15:02:56 +01:00
commit bc883deed4
199 changed files with 0 additions and 18851 deletions

View file

@ -1,7 +0,0 @@
jw-build Changes File
---------------------
Version 1.0.0-0
---------------
Split off from from ytools 1.2.14-12. Removed everything which isn't directly
meaningful to software build and packaging functionality.

225
README.md
View file

@ -1,225 +0,0 @@
# JW-Build
## Features
The JW-Build package is basically a bunch of scripts and GNU makefile snippets
for organizing software builds and releases.
You can install it to its standard location `/opt/jw-build`, or put it anywhere
you want in your file system, typically next to your own projects in the same
directory. To organize their respective builds, you can then include JW-Build's
makefile snippets from your own projects' makefiles, like so:
include $(JWBDIR)/make/cpp.mk
where `JWBDIR` needs to point to JW-Build's installation directory. In this
example, the snippet `cpp.mk` would by default take all C++ files it finds in
the directory from where its included, compile them, and and add them to a
shared project library. It would also take all header files and copy them to a
project include directory. `js.mk` would by default minify all JavaSript it
finds, `java.mk` jar up .java files into classes and jar-files, and so on.
JW-Build also handles installation and packaging of these files, to
customizable locations with standardish defaults.
JW-Build is small, its tarball is about 200K. It's small enough to be shipped
with the source code of your project, if you choose to do so. And it's small
enough to be self-documenting. Well, okay, somewhat self-documenting. You have
to know GNU Makefile syntax to understand what it does, and dig into its
somtimes arcane code, ideally with a working example. You can install it with
your distribution's package manager, or you can keep it within your code
versioning system, alongside your own code. It's also designed to be the
lightest possible touch on any given source code package, in terms of code you
need to add to a given package that should be built with it, and also in terms
of software packages needed to be installed on your machine. This way, it's
easily added - and it's also easy to replace, should you choose to do so at
some point. You will then have all your settings like file system path
definitions and compiler flags in well-defined places already.
JW-Build runs a recursive make, so, with a few exceptions such as submodules,
you will need a makefile in every directory with source code. Most, if not all
of these makefiles can be three-liners. This buys you convenience, minimal,
clean, humanly digestable code, and a structured way to customize builds
involving multiple packages - as centrally or as locally as you want. You can
override any of JW-Build's default variables - for many packages, for an entire
package, or for any subdirectory of a given package, at your option. You can
write your own snippets and reuse them in multiple places. You can keep
overrides in your versioning system or add them where needed in
`local.mk`-files, which only your machine knows about. Or you can use
environment variables, of course. JW-Build intentionally avoids makefile code
generation as seen with CMake or GNU Autotools. This keeps the code small and
readable for easy debugging. Okay, for relatively easy debugging. To achieve
this, JW-Build has to detect a couple of things in every directory it enters,
but it uses various caching mechanisms to keep builds still reasonably fast.
JW-Build has makefile snippets for building libraries and executables, snippets
that output code compiled from C/C++, Python, Java, JavaScript, LaTeX, SWIG and
other input formats, and it's easily extendible to support any given
programming language or task. It's in use at janware for managing sub-builds of
Maven, Ant, CMake and others, and for packaging the results. It provides
targets to flash binaries onto microcontrollers, produce Debian, RPM and IPK
packages, install them locally or remotely, or feed them into DevOps pipelines,
taking note of released versions within GIT, SVN or CVS. It detects whether or
not a package needs a new release because its source code changed. Or because a
package it depends on has changed incompatibly. JW-Build has targets for
collaboration over structured sets of remote Git repositories. It supports a
simple configuration file per package for specifying package metadata, e.g. its
dependencies, license, description, pre- and postinstall scriptlets, and so on.
It has a SAT-solver built in, for building multiple packages in the right
order, based on that metadata. With the same metadata, it can also
automatically generate BitBake recipes and run Yocto-builds incorporating your
software. Packages which are not organized with JW-Build can also be integrated
into the build. It generates runtime, development and source code package
variants. It supports cross compilation with MinGW and the GNU toolchain. It's
tested on Debian, Ubuntu, OpenSUSE, Fedora / CentOS / RHEL, and many Unices.
JW-Build is designed to be friendly to both developers and integrators.
Developers can cd into any given directory, edit the source code, run `make`,
and expect the resulting binaries to work and be immediately testable, for a
workflow that lets you focus on coding in your target language. For integrators
on the other hand, a hotfix on a server or an embedded host can be as simple as
TARGET_HOST=myserver.acme.com make pkg-remote-install
And of course, it can build, package and release itself. Without being
installed, which is a Good Thing (TM).
## Basic Usage
### For janware builds
See https://janware.com/wiki/pub/sw/build/ for documentation on how to get
and use JW-Build within the janware build infrastructure.
### Standalone
If you want to use it standalone, OTOH, do the following to get a minimal
working example:
First, add a `make` subdirectory to the toplevel directory of your package,
containing two files:
1. `proj.mk`, containing a definition of `JWBDIR`, pointing to the JW-Build
installation directory, e.g. like so:
JWBDIR ?= $(firstword $(wildcard $(addsuffix /jw-build,$(TOPDIR)/.. /opt)))
`TOPDIR` points to, you guessed it, the toplevel directory of your package.
You will most likely define it yourself in every makefile that uses
`proj.mk`, see below. The right-hand side of the equation is GNU Make
gibberish for: *"Look for a directory named `jw-build` next to my package,
and then below `/opt`, in that order."* Assuming that's where the packages
are in your file system.
Things to note:
- All directory paths can be relative, which is nice if you want to
organize multiple packages in a fixed tree layout, but want them to work
wherever you place the tree.
- It doesn't have to be `$(TOPDIR)/make`. You can choose any other
subdirectory of your package, but for now let's just assume it's
`$(TOPDIR)/make`, the default location.
2. `project.conf`, containing
[description]
A frobnicator library
Then, add files named `Makefile` to the directories of your project,
containing, e.g., in a C++ directory:
TOPDIR = ../..
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/cpp.mk
Done. Well, in principle. Other notable snippets are `topdir.mk` for the
toplevel directory, `dirs.mk` for other directories with subdirectories,
`lib.mk` for the directory containing the package's main library, which
defaults to `$(TOPDIR)/lib`, `bin.mk` for `$(TOPDIR)/bin`, `include.mk` for
`$(TOPDIR)/include`, and `make.mk` for `$(TOPDIR)/make`. You should add them in
the same manner. Again, these are just default locations. Once you've added
those makefiles, running `make` will do - something. Try and see what happens.
Every snippet supports at least the targets `all`, `install`, `clean` and
`distclean`. The target `echo-makefiles` shows you all included snippets,
`cat-makefiles` concatenates them. Hitting TAB should show you all targets
supported in a particular directory.
Good luck!
## Advanced Usage, Custom Makefiles, Tips and Tricks, Things to Note
- JW-Build will use any `Makefile`, `makefile` or `GNUmakefile` it finds in the
toplevel directory of your package. It will `cd` into the toplevel directory
and run `make` during build runs, and subsequently `make install` during
installation runs. It will also run `make clean` if invoked from outside.
`make distclean` doesn't need to be supported, but comes in handy, if you
want your packages to be wiped extra-clean.
JW-Build will not run `make install` as the `root` user, and will therefore
expect you to use `$(INSTALL)` instead of `/usr/bin/install`, to which it is
command line compatible.
[pseudo](http://git.yoctoproject.org/cgit/cgit.cgi/pseudo) support is
underway and will allow to use plain `/usr/bin/install`, but is not yet
implemented.
- If you want GNU Make to do what it's designed for for your custom task, i.e.
do the right thing based on file modification times, do the following, for
example:
TOPDIR = ../..
MY_CREATION_INPUT = $(wildcard *.tmpl)
MY_CREATION = $(patsubst %.tmpl,%,$(MY_CREATION_INPUT))
MY_INSTALL_DIR = $(ENV_PREFIX)/var/lib/my-creation
MY_INSTALLED_CREATION = $(addprefix $(MY_INSTALL_DIR)/,$(MY_CREATION))
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/defs.mk
all: $(MY_CREATION)
install: $(MY_INSTALLED_CREATION)
clean: clean.my-creation
distclean: clean
%: %.tmpl
bash ./my-special-stuff-creator.sh $< > $@.tmp
mv $@.tmp $@
clean.my-creation:
rm -f $(MY_CREATION) *.tmp
$(MY_INSTALL_DIR):
$(INSTALL) -o root -g root -m 755 -d $@
$(MY_INSTALL_DIR)/%: % | $(MY_INSTALL_DIR)
$(INSTALL) -o root -g root -m 644 $< $@
Things to note:
- If the example seems too verbose for you, consider putting the code into
`$(TOPDIR)/make/my-creation.mk` (for example) and `include` that.
- `defs.mk` doesn't provide any targets, but only defines central variables.
It's implicitly included with most snippets, but if you want to define your
own tasks, you can use it directly.
- The `MY_XXX` variables have arbitrary names and are not evaluated by
JW-Build.
- `$(ENV_PREFIX)` will automatically point to something below your home
directory if invoked from a package which has `.git`, `.svn` or `CVS` in its
toplevel directory, and to the proper target root during package creation.
- Using the intermediate `$@.tmp` is a good idea in case
`my-special-stuff-creator.sh` can fail.
- See `info make` for how pattern rules work (`%`), what the `|` pipe -
symbol is for and all that jazz. If you don't know already.
- If you want to add arbitrary tasks to the build run, consider the following
makefile:
```
TOPDIR = ../..
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/defs.mk
all: my-task.done
clean: clean.my-task
my-task.done:
cd $(SUBMOD_SRC_DIR) && mvn -DskipTests --settings ../maven-settings.xml
touch $@
clean.my-task:
rm -rf $(addprefix $(SUBMOD_SRC_DIR)/,dependency-reduced-pom.xml externs/target target) $(SOURCE_BASE)
rm -f *.done
```
[logo]: https://janware.com/janware/images/logo-janware/logo-janware-200.png

View file

@ -1,35 +0,0 @@
########################################################################
# #
# development utilities #
# (c) 2001 jannet it services #
# Authors: Jan Lindemann #
# contact@jannet.de #
# patches, bugfixes and comments are welcome at patch@jannet.de #
# #
# $Id$
# #
# This program is free software; permission to use, copy, modify, #
# distribute, and sell this software and its documentation under the #
# terms of the GNU Public license as published by the Free Software #
# Foundation, either version 2 or any later version of the license, is #
# hereby granted without fee, provided that (i) the above copyright #
# notices and this permission notice appear in all copies of the #
# software and related documentation, and (ii) the name of jannet may #
# not be used in any advertising or publicity relating to the software #
# without the specific, prior written permission of jannet. #
# #
# This program is distributed in the hope that it will be useful, but #
# WITHOUT ANY WARRANTY; without even the implied warranty of MERCHAN- #
# TABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General #
# Public License for more details. #
# #
# You should have received a copy of the GNU General Public License #
# along with this program; if not, write to the Free Software Founda- #
# tion, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. #
# #
########################################################################
TOPDIR = ..
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/bin.mk

View file

@ -1,4 +0,0 @@
TOPDIR = ..
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/dirs.mk

View file

@ -1,9 +0,0 @@
TOPDIR = ../..
INSTALL_CFGDIR = $(ENV_PREFIX)/etc
CFGMODE = 644
LOCAL_CFG = jw-rc.status
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/conf.mk

View file

@ -1,463 +0,0 @@
# /etc/rc.status
# vim: syntax=sh
# Definition of boot script return messages
#
# The bootscripts should use the variables rc_done and rc_failed to
# report whether they failed or succeeded. See /etc/init.d/skeleton for
# an example how the shell functions rc_status and rc_reset are used.
#
# These functions make use of the variables rc_done and rc_failed;
# rc_done_up and rc_failed_up are the same as rc_done and rc_failed
# but contain a terminal code to move up one line before the output
# of the actual string. (This is particularly useful when the script
# starts a daemon which produces user output with a newline character)
#
# The variable rc_reset is used by the master resource control script
# /etc/init.d/rc to turn off all attributes and switch to the standard
# character set.
#
# \033 ascii ESCape
# \033[<NUM>G move to column <NUM> (linux console, xterm, not vt100)
# \033[<NUM>C move <NUM> columns forward but only upto last column
# \033[<NUM>D move <NUM> columns backward but only upto first column
# \033[<NUM>A move <NUM> rows up
# \033[<NUM>B move <NUM> rows down
# \033[1m switch on bold
# \033[31m switch on red
# \033[32m switch on green
# \033[33m switch on yellow
# \033[m switch off color/bold
# \017 exit alternate mode (xterm, vt100, linux console)
# \033[10m exit alternate mode (linux console)
# \015 carriage return (without newline)
#
# Check if the service is used under systemd but not started with
if test -z "$SYSTEMD_NO_WRAP" && /usr/bin/mountpoint -q /sys/fs/cgroup/systemd; then
if test $PPID -ne 1 -a $# -eq 1 ; then
_rc_base=
_sd_opts=
case "$0" in
/etc/init.d/boot.*)
_rc_base=${0##*/boot.} ;;
/etc/init.d/*|/etc/rc.d/*)
_rc_base=${0##*/} ;;
*/rc*)
if test -L "$0"; then
_rc_base=`readlink "$0"`
_rc_base=${_rc_base##*/}
case "$_rc_base" in
boot.*) _rc_base=${_rc_base#boot.}
esac
else
_rc_base=${0##*/rc}
fi
;;
esac
_rc_system=$(/usr/bin/systemctl show --system --no-pager -p NeedDaemonReload \
-p UnitFileState -p LoadState "${_rc_base}.service" 2>/dev/null)
case "$_rc_system" in
*LoadState=masked*)
echo "Error: ${_rc_base} is masked out and forbidden by systemd" 1>&2
exit 2 ;;
*UnitFileState=static*)
echo "Skipped: ${_rc_base} is overwritten by a native systemd unit" 1>&2
exit 2 ;;
*NeedDaemonReload=yes*)
/usr/bin/systemctl --system --no-pager daemon-reload
esac
unset _rc_system
case "$1" in
status)
SYSTEMD_NO_WRAP=1 "$0" "$1"
_sd_opts='--lines=0 --full --output=cat'
;;
start|stop|reload|restart|try-restart|force-reload)
echo "redirecting to systemctl $1 ${_rc_base}.service" 1>&2
_sd_opts='--ignore-dependencies'
;;
*) unset _rc_base
esac
if test -n "$_rc_base" -a -x /usr/bin/systemctl ; then
exec /usr/bin/systemctl $_sd_opts $1 "${_rc_base}.service"
fi
unset _rc_base _sd_opts
fi
if test -z "$REDIRECT" -a -x /sbin/showconsole ; then
REDIRECT="$(/sbin/showconsole 2>/dev/null)"
test -z "$CONSOLE" && CONSOLE=/dev/console
export REDIRECT CONSOLE
fi
fi
# Do _not_ be fooled by non POSIX locale
LC_ALL=POSIX
export LC_ALL
# Seek for terminal size and, if needed, set default size
rc_lc () {
if test -n "$REDIRECT" ; then
set -- $(stty size < "$REDIRECT" 2> /dev/null || echo 0 0)
else
set -- $(stty size 2> /dev/null || echo 0 0)
fi
LINES=$1
COLUMNS=$2
if test $LINES -eq 0 -o $COLUMNS -eq 0; then
LINES=24
COLUMNS=80
TERM=dumb
fi
}
trap 'rc_lc' SIGWINCH
test -n "$COLUMNS" -a -n "$LINES" || rc_lc
export LINES COLUMNS
# Make sure we have /sbin and /usr/sbin in PATH
case ":$PATH:" in
*:/sbin:*)
;;
*)
PATH=/sbin:/usr/sbin:/usr/local/sbin:$PATH
export PATH
;;
esac
if test -t 1 -a "$TERM" != "raw" -a "$TERM" != "dumb"; then
esc=`echo -en "\033"`
extd="${esc}[1m"
warn="${esc}[1;31m"
done="${esc}[1;32m"
attn="${esc}[1;33m"
norm=`echo -en "${esc}[m\017"`
stat=`echo -en "\015${esc}[${COLUMNS}C${esc}[10D"`
rc_done="${stat}${done}done${norm}"
rc_running="${stat}${done}running${norm}"
rc_failed="${stat}${warn}failed${norm}"
rc_missed="${stat}${warn}missing${norm}"
rc_skipped="${stat}${attn}skipped${norm}"
rc_dead="${stat}${warn}dead${norm}"
rc_unused="${stat}${extd}unused${norm}"
rc_unknown="${stat}${attn}unknown${norm}"
rc_done_up="${esc}[1A${rc_done}"
rc_failed_up="${esc}[1A${rc_failed}"
rc_reset="${norm}${esc}[?25h"
rc_save="${esc}7${esc}[?25l"
rc_restore="${esc}8${esc}[?25h"
rc_cuu () { test $1 -eq 0 && return; echo -en "\033[${1}A"; }
rc_cud () { test $1 -eq 0 && return; echo -en "\033[${1}B"; }
rc_timer_on () {
# Draw seconds of running timout to column.
# Two arguments: timeout in seconds and offset
local n=$1
local c=$2
(trap "exit 0" SIGTERM
while test $((n--)) -gt 0; do
sleep 1;
if test $n -gt 9 ; then
echo -en "\015${esc}[${c}C(${n}s) "
else
echo -en "\015${esc}[${c}C( ${n}s) "
fi
done) & _rc_timer_pid=$!
}
rc_timer_off () {
if test -n "$_rc_timer_pid" ; then
kill -TERM $_rc_timer_pid > /dev/null 2>&1
fi
unset _rc_timer_pid
}
else
esc=""
extd=""
warn=""
done=""
attn=""
norm=""
stat=""
rc_done="..done"
rc_running="..running"
rc_failed="..failed"
rc_missed="..missing"
rc_skipped="..skipped"
rc_dead="..dead"
rc_unused="..unused"
rc_unknown="..unknown"
rc_done_up="${rc_done}"
rc_failed_up="${rc_failed}"
rc_reset=""
rc_save=""
rc_restore=""
rc_cuu () { return; }
rc_cud () { return; }
rc_timer_on () { return; }
rc_timer_off () { return; }
fi
_rc_service=${0##*/[SK][0-9][0-9]}
_rc_status=0
_rc_status_all=0
_rc_todo=$1
rc_check ()
{
_rc_status_ret=$?
test $_rc_status_ret -eq 0 || _rc_status=$_rc_status_ret
test $_rc_status -eq 0 || _rc_status_all=$_rc_status
return $_rc_status_ret
}
rc_reset ()
{
_rc_status=0
_rc_status_all=0
rc_check
return 0
}
if test "$_rc_todo" = "status" ; then
rc_status ()
{
rc_check
_rc_status_ret=$_rc_status
local i
for i ; do
case "$i" in
-v|-v[1-9]|-v[1-9][0-9])
local vrt=""
local out=1
local opt="en"
test -n "${i#-v}" && vrt=${esc:+"${esc}[${i#-v}A"} || opt="e"
case "$_rc_status" in
0) vrt="$vrt$rc_running"; ;; # service running
1) vrt="$vrt$rc_dead" ; out=2 ;; # service dead (but has pid file)
2) vrt="$vrt$rc_dead" ; out=2 ;; # service dead (but has lock file)
3) vrt="$vrt$rc_unused" ; ;; # service not running
4) vrt="$vrt$rc_unknown"; ;; # status is unknown
esac
echo -$opt "$rc_save$vrt$rc_restore" 1>&$out
# reset _rc_status to 0 after verbose case
_rc_status=0 ;;
-r) rc_reset ;;
-s) echo -e "$rc_skipped" ; rc_failed 3 ;;
-u) echo -e "$rc_unused" ; rc_failed 3 ;;
*) echo "rc_status: Usage: [-v[<num>] [-r]|-s|-u]" 1>&2 ; return 0 ;;
esac
done
return $_rc_status_ret
}
elif test -n "$_rc_todo" ; then
rc_status ()
{
rc_check
test "$_rc_status" -gt 7 && rc_failed 1
_rc_status_ret=$_rc_status
case "$_rc_todo" in
stop)
# program is not running which
# is success if we stop service
test "$_rc_status" -eq 7 && rc_failed 0 ;;
esac
local i
for i ; do
case "$i" in
-v|-v[1-9]|-v[1-9][0-9])
local vrt=""
local out=1
local opt="en"
test -n "${i#-v}" && vrt=${esc:+"${esc}[${i#-v}A"} || opt="e"
case "$_rc_status" in
0) vrt="$vrt$rc_done" ; ;; # success
1) vrt="$vrt$rc_failed" ; out=2 ;; # generic or unspecified error
2) vrt="$vrt$rc_failed" ; out=2 ;; # invalid or excess args
3) vrt="$vrt$rc_missed" ; out=2 ;; # unimplemented feature
4) vrt="$vrt$rc_failed" ; out=2 ;; # insufficient privilege
5) vrt="$vrt$rc_skipped"; out=2 ;; # program is not installed
6) vrt="$vrt$rc_unused" ; out=2 ;; # program is not configured
7) vrt="$vrt$rc_failed" ; out=2 ;; # program is not running
*) vrt="$vrt$rc_failed" ; out=2 ;; # unknown (maybe used in future)
esac
echo -$opt "$rc_save$vrt$rc_restore" 1>&$out
# reset _rc_status to 0 after verbose case
_rc_status=0 ;;
-r) rc_reset ;;
-s) echo -e "$rc_skipped" 1>&2 ; rc_failed 5 ;;
-u) echo -e "$rc_unused" 1>&2 ; rc_failed 6 ;;
*) echo "rc_status: Usage: [-v[<num>] [-r]|-s|-u]" 1>&2 ; return 0 ;;
esac
done
return $_rc_status_ret
}
else
rc_status ()
{
rc_check
_rc_status_ret=$_rc_status
local i
for i ; do
case "$i" in
-v|-v[1-9]|-v[1-9][0-9])
local vrt=""
local out=1
local opt="en"
test -n "${i#-v}" && vrt=${esc:+"${esc}[${i#-v}A"} || opt="e"
case "$_rc_status" in
0) vrt="$vrt$rc_done" ; ;; # success
*) vrt="$vrt$rc_failed"; out=2 ;; # failed
esac
echo -$opt "$rc_save$vrt$rc_restore" 1>&$out
# reset _rc_status to 0 after verbose case
_rc_status=0 ;;
-r) rc_reset ;;
-s) echo -e "$rc_skipped" ; return 0 ;;
-u) echo -e "$rc_unused" ; return 0 ;;
*) echo "rc_status: Usage: [-v[<num>] [-r]|-s|-u]" 1>&2 ; return 0 ;;
esac
done
return $_rc_status_ret
}
fi
rc_failed ()
{
rc_reset
case "$1" in
[0-7]) _rc_status=$1 ;;
"") _rc_status=1
esac
rc_check
return $_rc_status
}
rc_exit ()
{
exit $_rc_status_all
}
rc_confirm()
{
local timeout="30"
local answer=""
local ret=0
case "$1" in
-t) timeout=$2; shift 2 ;;
esac
local message="$@, (Y)es/(N)o/(C)ontinue? [y] "
: ${REDIRECT:=/dev/tty}
while true ; do
read -t ${timeout} -n 1 -p "${message}" answer < $REDIRECT > $REDIRECT 2>&1
case "$answer" in
[yY]|"") ret=0; break ;;
[nN]) ret=1; break ;;
[cC]) ret=2; break ;;
*) echo; continue
esac
done
echo
return $ret
}
rc_active ()
{
local link
for link in /etc/init.d/*.d/S[0-9][0-9]${1} ; do
test -e $link || break
return 0
done
return 1
}
rc_splash()
{
return 0
}
# Wait between last SIGTERM and the next SIGKILL
# any argument specify a *path* of a process which
# process identity should *not* be checked.
rc_wait()
{
local -i etime=$SECONDS
if test -f /fastboot ; then
let etime+=2
else
let etime+=6
fi
local -i pid
local -i ppid=$$
local comm state rest
local parent_processes="$ppid"
while test $ppid -gt 1; do
read -t 1 pid comm state ppid rest < /proc/$ppid/stat
parent_processes="${parent_processes:+$parent_processes:}${ppid}"
done
for comm ; do
test -s $comm || continue
ppid="$(/sbin/pidofproc $comm 2> /dev/null)" || continue
parent_processes="${parent_processes:+$parent_processes:}${ppid}"
done
unset comm state ppid rest
local -i busy
while test $SECONDS -lt $etime; do
let busy=0
for proc in /proc/[0-9]* ; do
test -e $proc/exe || continue
let pid=${proc##*/}
case ":${parent_processes}:" in
*:${pid}:*) continue
esac
let busy=pid
break
done
test $busy -ne 0 || return 0
usleep 500000
done
}
rc_runlevel()
{
test -z "$RUNLEVEL" || return
set -- $(/sbin/runlevel)
PREVLEVEL=$1
RUNLEVEL=$2
export PREVLEVEL RUNLEVEL
}
cmdline=""
rc_cmdline()
{
local arg cmd key val
test -e /proc/cmdline || mount -nt proc proc /proc
test -n "$cmdline" || read -t 2 cmdline < /proc/cmdline
for arg; do
for cmd in $cmdline ; do
key="${cmd%%=*}"
key="${key//-/_}"
case "${key}" in
$arg)
case "$cmd" in
*=*) val="${cmd#*=}" ;;
*) val=yes
esac
echo $key=$val
return 0
esac
done
done
return 1
}

View file

@ -1,9 +0,0 @@
TOPDIR = ../..
SUBTREE_INSTALL_PREFIX ?= /etc/jcs
SUBTREE_FILES += ./templates/dir/module/Makefile ./templates/dir/src/Makefile
SUBTREE_DIRS += $(sort $(dir $(SUBTREE_FILES)))
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/subtree.mk
include $(JWBDIR)/make/dev-utils.mk

View file

@ -1,8 +0,0 @@
jcs_dir=$HOME/local/src/jw.dev/conf/`sed 's|\([^.]\+\)\.\(.*\)|\2/\1|' /etc/hostname`/`/opt/jw-build/bin/get-os.sh`
jcs_owner=root
jcs_group=root
jcs_log_dir=$jcs_dir/log
jcs_file_extension=inf
use_checksum=false
update_checksum_command="/home/tripwire/bin/fs_checksum.sh update"
jcs_http_path=http://www.jannet.de

View file

@ -1,122 +0,0 @@
SHELL = /bin/sh
WD := $(shell pwd)
MOD := $(shell pwd | xargs basename)
LOG_DIR := $(shell . /etc/jcs/jcs.conf; echo $$jcs_log_dir)
INSTALL_LOG := $(LOG_DIR)/install.log
SETUP_LOG := $(LOG_DIR)/setup.log
TEE := /usr/bin/tee
BINDIR := /usr/local/bin
SBINDIR := /usr/local/bin
INF := $(wildcard *.inf)
INF_DONE := $(addsuffix .done,$(basename $(INF)))
INF_SU_DONE := $(addsuffix .su_done,$(basename $(INF)))
JCS_HTTP_PATH := $(shell . /etc/jcs/jcs.conf; echo $$jcs_http_path)
JCS = /opt/jw-build/bin/jcs
export SETUP_LOG INSTALL_LOG TEE BINDIR SBINDIR
all:
define recurse_subdirs
@set -e ;\
TARGET=$@ ;\
N="`echo $(SUBDIRS) | wc -w`" ;\
I=1 ;\
while [ $$I -le $$N ] ; do \
SUBDIR="`echo $(SUBDIRS) | cut -d' ' -f$$I`" ;\
$(MAKE) -C $$SUBDIR $$TARGET;\
I=`expr $$I + 1`;\
done
endef
%.done: %.inf
sudo $(JCS) install $<
touch $@
%.su_done: %.inf
sudo $(JCS) install -b setup -f $<
touch $@
install_inf: $(INF_DONE)
install_inf.old: checkroot checkdirs
@echo "####" checking installation information files ... ;\
if [ -n "`find . -name '*.inf' -maxdepth 1`" ] ; then \
sudo $(JCS) install *.inf ;\
fi | $(TEE) -a $(INSTALL_LOG)
install_link:
install_link.old: checkroot checkdirs
@echo "####" checking link information files ... ;\
if [ -e link.sh ] ; then \
$(JCS) linkout link.sh -b install ;\
fi | $(TEE) -a $(INSTALL_LOG)
setup_inf: $(INF_SU_DONE)
setup_inf.old: checkroot checkdirs
@echo "####" checking installation information files ... ;\
if [ -n "`find . -name '*.inf' -maxdepth 1`" ] ; then \
sudo $(JCS) install -b setup -f *.inf ;\
fi | $(TEE) -a $(SETUP_LOG)
setup_link: checkroot checkdirs
@echo "####" checking link information files ... ;\
if [ -e link.sh ] ; then \
$(JCS) linkout -f -b setup link.sh ;\
fi | $(TEE) -a $(SETUP_LOG)
test_inf: checkdirs
@echo "####" testing installation information files ... ;\
if [ -n "`find . -name '*.inf' -maxdepth 1`" ] ; then \
sudo $(JCS) install *.inf -t ;\
fi | $(TEE) -a $(INSTALL_LOG)
test_link: checkdirs
@echo "####" testing link information files ... ;\
if [ -e link.sh ] ; then \
$(JCS) linkout -t link.sh ;\
fi | $(TEE) -a $(INSTALL_LOG)
get: checkdirs
@echo "####" getting files. ;\
if [ -n "$(GETFILES)" ] ; then $(JCS) get $(GETFILES) ; fi
getall: $(LOCAL_GET) get $(LOCAL_POST_GET)
$(recurse_subdirs)
checksum: checkroot # TODO integrate tripwire
@if [ "$$cfg_use_checksum" = TRUE ] ; then \
echo "####" updating checksum database ... ;\
$$update_checksum_command ;\
fi
install: checkroot $(LOCAL_INSTALL) install_inf install_link $(LOCAL_POST_INSTALL) checksum
$(recurse_subdirs)
setup: checkroot $(LOCAL_SETUP) setup_inf setup_link $(LOCAL_POST_SETUP) checksum
$(recurse_subdirs)
test: $(LOCAL_TEST) test_inf test_link $(LOCAL_POST_TEST)
$(recurse_subdirs)
dist: clean
cd ..;\
find $(MOD) -type f -o -type l | \
grep -ve "CVS\|trash\|$(MOD)/setup" | \
xargs tar -cvzf $(MOD).tar.gz ;\
mv $(MOD).tar.gz $(MOD)
checkroot:
# @if [ `whoami` != root ] ; then echo "Only root can do this." >&2; exit 1; fi
checkdirs:
@test -f /etc/jcs/jcs.conf || exit 1 ;\
test -d `dirname $(SETUP_LOG)` || mkdir -p `dirname $(SETUP_LOG)` ;\
test -d `dirname $(INSTALL_LOG)` || mkdir -p `dirname $(INSTALL_LOG)`
clean: $(LOCAL_CLEAN)
$(recurse_subdirs) ;\
rm -f *~ *.swp *.rep .\#* *.done *.su_done $(MOD).tar.gz default.cache 2>/dev/null

View file

@ -1,5 +0,0 @@
# jannet configuration shadow
# (c) 2000 - 2001 jannet
# contact@jannet.de
include /etc/jcs/jcs.mk

View file

@ -1,15 +0,0 @@
# jannet configuration shadow
# (c) 2000 jannet
# contact@jannet.de
MAKE_SH := jcs smake
SUBDIRS = cur
setup:
$(MAKE_SH) setup $(SUBDIRS)
install:
$(MAKE_SH) install $(SUBDIRS)
clean:
$(MAKE_SH) clean $(SUBDIRS)

View file

@ -1,4 +0,0 @@
TOPDIR = ../..
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/profile.mk

View file

@ -1,2 +0,0 @@
. /etc/jcs/jcs.conf
alias cdc="cd $jcs_dir"

View file

@ -1,3 +0,0 @@
CVSROOT=:ext:`whoami`@cvs.janware.com:/srv/cvs
CVS_RSH=/opt/jw-build/bin/jw-build-ssh.sh
export CVSROOT CVS_RSH

View file

@ -1,7 +0,0 @@
if [ -z "$PATH" ]; then
PATH=/opt/jw-build/bin
else
PATH=$PATH:/opt/jw-build/bin
fi
export PATH

View file

@ -1,6 +0,0 @@
TOPDIR = ..
SUBDIRS = licenses
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/dirs.mk

View file

@ -1,19 +0,0 @@
JW-Build Design Goals
---------------------
o Command-line and script friendly
o Self-contained, self-building
o Requires GNU-Make, Bash and Python
o Minimally invasive (3-liner Makefiles, if any at all)
o Support for cross compilation
o Sensible defaults, easily and flexibly customizable to build anything
o Allow changing into subdirectories for edit-compile-run cycles
o Build artifact caching (object files, packages)
o Work identically with and without installation
o Allow remote installation of packages
o Integration into versioning and packaging of corporate development workflow
o Allow inter-package dependencies to be coded, in-house and 3rd party
o Work with minimal documentation (i.e.: "Run make on janware.com/Makefile!")
o No undocumented steps
o Allow user privilege separation
o Allow web iterfaces for viewing

View file

@ -1,6 +0,0 @@
TOPDIR = ../..
INSTALL_DOCDIR = $(DOC_PREFIX)/licenses
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/doc.mk

View file

@ -1,502 +0,0 @@
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use,
not price. Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.
Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.
When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.
We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.
For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.
Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)
will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made with.
c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
d) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

View file

@ -1,4 +0,0 @@
TOPDIR = ../..
include $(TOPDIR)/make/proj.mk
include $(JWBDIR)/make/dummy.mk

Some files were not shown because too many files have changed in this diff Show more