From ffdd5523155204c2b9f5b6d18344b7148ed6db0c Mon Sep 17 00:00:00 2001 From: Andrew Andrianov Date: Tue, 8 Dec 2015 12:20:11 +0300 Subject: Add initial debian packaging info Signed-off-by: Andrew Andrianov diff --git a/debian/README b/debian/README new file mode 100644 index 0000000..c24d32d --- /dev/null +++ b/debian/README @@ -0,0 +1,6 @@ +The Debian Package crosstool-ng +---------------------------- + +Comments regarding the Package + + -- Andrew 'Necromant' Andrianov Mon, 07 Dec 2015 20:53:53 +0300 diff --git a/debian/changelog b/debian/changelog new file mode 100644 index 0000000..5404d63 --- /dev/null +++ b/debian/changelog @@ -0,0 +1,5 @@ +crosstool-ng (1.22.0git) unstable; urgency=low + + * Initial Debianized Release. + + -- Andrew 'Necromant' Andrianov Mon, 07 Dec 2015 20:53:53 +0300 diff --git a/debian/compat b/debian/compat new file mode 100644 index 0000000..ec63514 --- /dev/null +++ b/debian/compat @@ -0,0 +1 @@ +9 diff --git a/debian/control b/debian/control new file mode 100644 index 0000000..a9c9a76 --- /dev/null +++ b/debian/control @@ -0,0 +1,13 @@ +Source: crosstool-ng +Section: unknown +Priority: optional +Maintainer: Andrew 'Necromant' Andrianov +Build-Depends: debhelper (>= 9), autotools-dev, libncursesw5-dev, libncurses5-dev, autoconf, git, gperf, bison, flex, texinfo, help2man, gawk, subversion, git, gzip, bzip2, tar, libtool-bin, automake +Standards-Version: 3.9.5 +Homepage: http://crosstool-ng.org/ + +Package: crosstool-ng +Architecture: any +Depends: ${shlibs:Depends}, ${misc:Depends}, build-essential, texi2html, texinfo +Description: crosstool-ng + The ultimate tool to create your own cross toolchains diff --git a/debian/copyright b/debian/copyright new file mode 100644 index 0000000..9de636a --- /dev/null +++ b/debian/copyright @@ -0,0 +1,61 @@ +Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ +Upstream-Name: crosstool-ng +Source: + +Files: * +Copyright: 2015 Crosstool-NG Developers +License: GPL-2.0+ + +Files: debian/* +Copyright: 2015 Andrew 'Necromant' Andrianov +License: GPL-2.0+ + +License: GPL-2.0+ +Unless otherwise stated in individual files, this work is licensed to you under +the following terms. + +- Files in docs/ are available under the Creative Commons Attribution, Share + Alike (by-sa), v2.5, to be found there: + licenses.d/by-sa/deed.en (human-readable summary) + licenses.d/by-sa/legalcode (legal code, the full license) + +- Files found in patches/*/ are available under the same license as the + upstream software they apply to. + + That means that you can't use those patches if you were licensed the + software under a specific license which is not the one the software is + commonly available under. + + As an example, if you ever managed to get the Linux kernel under a license + other than the GPLv2, you are not allowed to use the Linux kernel patches + coming with crosstool-NG, as those are available under the GPLv2, which is + the license the Linux kernel is most commonly available under. + + As a convenience, the GNU Lesser General Public License (LGPL) v2.1 (for the + patches against glibc, uClibc, and some other libraries) is available there: + licenses.d/lgpl.txt + +- Other files not covered by the above licenses, and not covered by an + individual license specified in the file itself, or an accompanying file, + are available under the GNU General Public License (GPL), v2, to be found + here: + licenses.d/gpl.txt + +- Also, I want to clarify one point. If you build a toolchain with crosstool-NG + and you happen to sell, deliver, or otherwise publish this toolchain to a + third party, I consider crosstool-NG as being part of the sources needed to + rebuild the afore-mentioned toolchain, alongside with all other source code + that third party is otherwise entitled to receive, due to other licenses of + the different components. See licenses.d/gpl.txt, section 3, which reads: + > For an executable work, complete source code means [...], plus the + > scripts used to control compilation and installation of the executable. + + In short: crosstool-NG is the part refered to as "the scripts to control + compilation and installation of the executable", it being the toolchain in + our case; and as such you must make it available, in conformance to the + GPLv2, see above. + + Also, if you have local patches that you apply to the different components + (either manualy, or by instructing crosstool-NG to do so), you will have to + make those patches available alongside with your toolchain, to comply with + the licenses of the components impacted by your patches. diff --git a/debian/docs b/debian/docs new file mode 100644 index 0000000..6f77277 --- /dev/null +++ b/debian/docs @@ -0,0 +1,2 @@ +README.md +TODO diff --git a/debian/rules b/debian/rules new file mode 100755 index 0000000..7dff29c --- /dev/null +++ b/debian/rules @@ -0,0 +1,31 @@ +#!/usr/bin/make -f +# See debhelper(7) (uncomment to enable) +# output every command that modifies files on the build system. +#DH_VERBOSE = 1 + +# see EXAMPLES in dpkg-buildflags(1) and read /usr/share/dpkg/* +DPKG_EXPORT_BUILDFLAGS = 1 +include /usr/share/dpkg/default.mk + +# see FEATURE AREAS in dpkg-buildflags(1) +#export DEB_BUILD_MAINT_OPTIONS = hardening=+all + +# see ENVIRONMENT in dpkg-buildflags(1) +# package maintainers to append CFLAGS +#export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic +# package maintainers to append LDFLAGS +#export DEB_LDFLAGS_MAINT_APPEND = -Wl,--as-needed + + +# main packaging script based on dh7 syntax +%: + MAKELEVEL=0 dh $@ --with autotools-dev + +# Make sure we call ./bootstrap before running dh_auto_configure +override_dh_auto_configure: + ./bootstrap && dh_auto_configure + +#Make sure to include bash completion file in the package +override_dh_auto_install: + MAKELEVEL=0 dh_auto_install + install -D ct-ng.comp $$(pwd)/debian/crosstool-ng/etc/bash_completion.d/ct-ng.comp diff --git a/debian/source/format b/debian/source/format new file mode 100644 index 0000000..89ae9db --- /dev/null +++ b/debian/source/format @@ -0,0 +1 @@ +3.0 (native) -- cgit v0.10.2-6-g49f6