EVERYTHING FROM THE OTHER REPO

2026-07-29 03:36:26 +03:00
parent 6777ea96db
commit 92a6ae42f5
4426 changed files with 1696506 additions and 2 deletions
@@ -0,0 +1,15 @@
+Building with the diet libc
+---------------------------
+
+This package optionally can be built with the diet libc instead of the
+glibc to provide small statically linked programs.  The resulting package
+has no dependency on any other package.
+
+To use the diet libc, make sure the latest versions of the dietlibc-dev
+package is installed, and set DEB_BUILD_OPTIONS=diet in the environment
+when building the package, e.g.:
+
+ # apt-get install dietlibc-dev
+ $ DEB_BUILD_OPTIONS=diet fakeroot apt-get source -b dash
+
+ -- Gerrit Pape <pape@smarden.org>, Wed, 23 Jun 2004 05:11:20 +0000
@@ -0,0 +1,85 @@
+Dash sources for Debian
+-----------------------
+
+The dash Debian package sources are available through git, and
+through 'apt-get source dash'.  Getting the sources through git
+should be preferred:
+
+    # apt-get install git  # if not yet done
+
+    $ git clone https://salsa.debian.org/debian/dash.git
+    $ cd dash
+
+After cloning the repository, you have checked out the debian/master
+branch, ready to be used by dpkg-buildpackage, e.g.
+
+    $ dpkg-buildpackage -i -uc -us
+
+If you want to make changes in the ./debian/ subdirectory, this is the
+correct branch to work on.  After making changes, document them in
+debian/changelog, and commit through 'git add' and 'git commit', or 'git
+commit -a', or similar.  If you think the changes should be incorporated
+into the standard Debian package, create the patch[es] through 'git
+format-patch', and send them to the Debian Bug Tracking System, e.g.
+
+    $ vi debian/rules
+    $ debchange -pi
+    $ git commit -a
+    $ git format-patch HEAD^
+
+This package uses 3.0 (quilt) format, which means patches to the upstream
+sources are stored in debian/patches, and are automatically applied by
+dpkg-source and dpkg-buildpackage.
+
+If you want to make changes to the upstream dash sources, be aware that
+debian/master branch doesn't have patches applied to the upstream sources.
+Should you prefer working with git to manage patches rather than quilt,
+you need to fetch a branch with patches applied from dgit.
+
+    $ dgit fetch
+
+The dgit/sid branch holds patches on top of the current release version
+that is packaged for Debian unstable. For each release, there are
+two tags: debian/* for patches-unappliedn, archive/debian/* for
+patches-applied.
+
+After checking out the dgit/sid branch, make the desired changes
+to the upstream sources, and commit them.  To integrate the changes into
+the Debian package, extract these changes, and change to the debian/master
+branch.
+
+    $ git format-patch dgit/dgit/sid..dgit/sid
+    $ git checkout debian/master
+
+Now move the extracted patches into the debian/patches/ directory, add the
+patch to the debian/patches/series, add a meaningful message to
+debian/changelog, and commit the changes to the debian/master branch
+
+    $ mv *.patch debian/patches/
+    $ git add debian/patches
+    $ debchange -pi
+    $ git add debian/changelog
+    $ git commit
+
+Again, if you think the changes should be incorporated into the standard
+Debian package, create the patch[es] from the debian/master branch through
+'git format-patch', send them to the Debian Bug Tracking System.
+
+As an addition to sending patches to the Debian Bug Tracking System, it is
+also possible to put your changes in a Git branch on Salsa and issue a pull
+request, mentioning that in your bug report.
+
+Uploading the package
+---------------------
+
+Uploads are currently handled by dgit. After you have prepared your changes, run:
+
+    dgit --gbp build-source
+
+This will build .dsc and _source.changes in the directory above. When done, run:
+
+    dgit --gbp push
+
+It will verify the source package, refresh the dgit branch, sign the source package,
+upload it to the Debian archive, create signed tags for the newly uploaded release,
+and push the dgit branch with tags to the dgit server.
@@ -0,0 +1,83 @@
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Upstream-Name: dash
+Upstream-Contact: dash@vger.kernel.org
+Source: http://gondor.apana.org.au/~herbert/dash/
+
+Files: *
+Copyright:
+ 1989-1994 The Regents of the University of California.  All rights reserved.
+ 1997 Christos Zoulas.  All rights reserved.
+ 1997-2021 Herbert Xu <herbert@gondor.apana.org.au>.  All rights reserved.
+Comment:
+ This code is derived from software contributed to Berkeley by Kenneth Almquist.
+License: BSD-3-Clause
+
+Files: src/bltin/test.c
+Copyright: Erik Baalbergen, Eric Gisin, Arnold Robbins, J.T. Conklin
+License: public-domain
+ This program is in the Public Domain.
+
+Files: src/mksignames.c
+Copyright: 1992, 1996, 1997, 1999, 2000, 2002-2012, Free Software Foundation, Inc.
+Comment: This file is not directly linked with dash.  However, its output is.
+License: GPL-2+
+
+Files: debian/*
+Copyright:
+ 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, Herbert Xu <herbert@debian.org>
+ 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2012, 2014, Gerrit Pape <pape@smarden.org>
+ 2009, Luk Claes <luk@debian.org>
+ 2010, 2011, Jonathan Nieder <jrnieder@gmail.com>
+ 2010, Adam D. Barratt <adam@adam-barratt.org.uk>
+ 2010, Christian Perrier <bubulle@debian.org>
+ 2013, Michael Gilbert <mgilbert@debian.org>
+ 2016, Helmut Grohne <helmut@subdivi.de>
+ 2016, Mattia Rizzolo <mattia@debian.org>
+ 2016, Niels Thykier <niels@thykier.net>
+ 2017, Adam Borowski <kilobyte@angband.pl>
+ 2017, Ximin Luo <infinity0@debian.org>
+ 2018—2021, Andrej Shadura <andrewsh@debian.org>
+License: BSD-3-clause
+
+License: BSD-3-clause
+ Redistribution and use in source and binary forms, with or without
+ modification, are permitted provided that the following conditions
+ are met:
+ 1. Redistributions of source code must retain the above copyright
+    notice, this list of conditions and the following disclaimer.
+ 2. Redistributions in binary form must reproduce the above copyright
+    notice, this list of conditions and the following disclaimer in the
+    documentation and/or other materials provided with the distribution.
+ 3. Neither the name of the University nor the names of its contributors
+    may be used to endorse or promote products derived from this software
+    without specific prior written permission.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+ ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+ FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ SUCH DAMAGE.
+
+License: GPL-2+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2, or (at your option)
+ any later version.
+ .
+ This program 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
+ 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 Foundation,
+ Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
+ .
+ On Debian systems, the complete text of the GNU General Public License
+ version 2 can be found in ‘/usr/share/common-licenses/GPL-2’.