[neon/backports-jammy/libunibreak-jammy/Neon/unstable] /: initial release
Carlos De Maine
null at kde.org
Mon Feb 20 22:39:07 GMT 2023
Git commit a99046f39c269fe2227c36d8d9154867da9e1b2a by Carlos De Maine.
Committed on 20/02/2023 at 22:39.
Pushed by carlosdem into branch 'Neon/unstable'.
initial release
(cherry picked from commit 8671e9c04b6c1c12d1323a7de1541abb53acefbb)
D +0 -92 README.md
A +58 -0 debian/README.source
A +223 -0 debian/changelog
A +1 -0 debian/compat
A +39 -0 debian/control
A +90 -0 debian/copyright
A +3 -0 debian/libunibreak-dev.install
A +0 -0 debian/libunibreak-doc.install
A +1 -0 debian/libunibreak5.install
A +13 -0 debian/rules
A +3 -0 debian/watch
https://invent.kde.org/neon/backports-jammy/libunibreak-jammy/commit/a99046f39c269fe2227c36d8d9154867da9e1b2a
diff --git a/README.md b/README.md
deleted file mode 100644
index d4c8d75..0000000
--- a/README.md
+++ /dev/null
@@ -1,92 +0,0 @@
-# libunibreak-jammy
-
-
-
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://invent.kde.org/neon/backports-jammy/libunibreak-jammy.git
-git branch -M master
-git push -uf origin master
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://invent.kde.org/neon/backports-jammy/libunibreak-jammy/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Automatically merge when pipeline succeeds](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
diff --git a/debian/README.source b/debian/README.source
new file mode 100644
index 0000000..5dde0bf
--- /dev/null
+++ b/debian/README.source
@@ -0,0 +1,58 @@
+This package uses quilt to manage all modifications to the upstream
+source. Changes are stored in the source package as diffs in
+debian/patches and applied during the build.
+
+To configure quilt to use debian/patches instead of patches, you want
+either to export QUILT_PATCHES=debian/patches in your environment
+or use this snippet in your ~/.quiltrc:
+
+ for where in ./ ../ ../../ ../../../ ../../../../ ../../../../../; do
+ if [ -e ${where}debian/rules -a -d ${where}debian/patches ]; then
+ export QUILT_PATCHES=debian/patches
+ break
+ fi
+ done
+
+To get the fully patched source after unpacking the source package, cd to
+the root level of the source package and run:
+
+ quilt push -a
+
+The last patch listed in debian/patches/series will become the current
+patch.
+
+To add a new set of changes, first run quilt push -a, and then run:
+
+ quilt new <patch>
+
+where <patch> is a descriptive name for the patch, used as the filename in
+debian/patches. Then, for every file that will be modified by this patch,
+run:
+
+ quilt add <file>
+
+before editing those files. You must tell quilt with quilt add what files
+will be part of the patch before making changes or quilt will not work
+properly. After editing the files, run:
+
+ quilt refresh
+
+to save the results as a patch.
+
+Alternately, if you already have an external patch and you just want to
+add it to the build system, run quilt push -a and then:
+
+ quilt import -P <patch> /path/to/patch
+ quilt push -a
+
+(add -p 0 to quilt import if needed). <patch> as above is the filename to
+use in debian/patches. The last quilt push -a will apply the patch to
+make sure it works properly.
+
+To remove an existing patch from the list of patches that will be applied,
+run:
+
+ quilt delete <patch>
+
+You may need to run quilt pop -a to unapply patches first before running
+this command.
diff --git a/debian/changelog b/debian/changelog
new file mode 100644
index 0000000..5766781
--- /dev/null
+++ b/debian/changelog
@@ -0,0 +1,223 @@
+libunibreak (5.1-1) unstable; urgency=medium
+
+ * Non maintainer upload by the Reproducible Builds team.
+ * No source change upload to rebuild on buildd with .buildinfo files.
+
+ -- Holger Levsen <holger at debian.org> Fri, 01 Jan 2021 15:29:20 +0100
+
+libunibreak (1.1-2) unstable; urgency=medium
+
+ * debian/libunibreak1-dev.install:
+ - Added pkgconfig files. (Closes: #784630)
+ * debian/control:
+ - Bumped Standards-Version to 3.9.6, no changes needed.
+
+ -- Eugene V. Lyubimkin <jackyf at debian.org> Thu, 14 May 2015 22:43:03 +0300
+
+libunibreak (1.1-1) unstable; urgency=low
+
+ * New upstream release.
+ * debian/control:
+ - Replaced 'liblinebreak' with 'libunibreak' in long descriptions.
+ (Closes: #717282)
+ - Updated Unicode reference URLs in long descriptions.
+ - Don't depend on quilt anymore.
+ * debian/copyright:
+ - Simplified and updated copyright years.
+ * debian/patches:
+ - 010-fix-building-without-static.patch: removed, applied upstream.
+ * debian/rules:
+ - Quilt is not used anymore.
+
+ -- Eugene V. Lyubimkin <jackyf at debian.org> Thu, 24 Oct 2013 21:56:38 +0300
+
+libunibreak (1.0-2) unstable; urgency=low
+
+ * debian/control:
+ - Added missing conflicts with liblinebreak{,2}-dev. (Closes: #710474)
+ * debian/watch:
+ - Adjusted to search for libunibreak, not for liblinebreak.
+
+ -- Eugene V. Lyubimkin <jackyf at debian.org> Sun, 07 Jul 2013 21:42:37 +0300
+
+libunibreak (1.0-1) unstable; urgency=low
+
+ * New upstream release.
+ * debian/copyright:
+ - Updated.
+ * debian/{control,liblinebreak*}:
+ - Content changes and file renames due to upstream rename.
+ * debian/control:
+ - Added quilt to Build-Depends.
+ - Added dh-autoreconf to Build-Depends.
+ - Bumped Standards-Version to 3.9.4, no changes needed.
+ * debian/rules:
+ - Fixed passing build prefix to ./configure.
+ - Use quilt's dh plugin.
+ - Use dh-autoreconf's dh plugin.
+ - Rewrote using dh override targets.
+ - Added dpkg-buildflags support.
+ * debian/patches:
+ - Added 010-fix-building-without-static.patch, cherry-picked from
+ upstream.
+ * debian/*.symbols:
+ - Recreated for new upstream name.
+ * debian/README.source:
+ - Added with quilt instructions.
+ * debian/NEWS:
+ - Removed as obsolete.
+
+ -- Eugene V. Lyubimkin <jackyf at debian.org> Sun, 19 May 2013 19:35:02 +0300
+
+liblinebreak2 (2.1-1) unstable; urgency=low
+
+ * New upstream release.
+ * debian/copyright:
+ - Updated copyright years.
+ - Updated Unicode page reference.
+ * debian/control:
+ - Updated Unicode page reference.
+ - Bumped Standards-Version to 3.9.2, no changes needed.
+
+ -- Eugene V. Lyubimkin <jackyf at debian.org> Sat, 01 Oct 2011 14:06:36 +0300
+
+liblinebreak2 (2.0-1) unstable; urgency=low
+
+ * New upstream release.
+ * debian/control:
+ - Bumped Standards-Version to 3.9.1, no changes needed.
+ - Updated package names: 'liblinebreak' -> 'liblinebreak2'.
+ - Updated links to the Unicode documentation in the long descriptions.
+ - Updated my mail address.
+ - Removed 'DM-Upload-Allowed' flag, not needed anymore.
+ - 'liblinebreak2-dev' conflicts with 'liblinebreak-dev'.
+ * debian/changelog:
+ - Changed source package name to liblinebreak2 since API is changed.
+ * debian/copyright:
+ - Updated copyright years.
+ * debian/{liblinebreak -> liblinebreak2}-dev.install:
+ - Don't install .la file.
+ * debian/{liblinebreak -> liblinebreak2}-doc.install
+ - Updated documentation path.
+ * debian/{liblinebreak -> liblinebreak2}-doc.doc-base.reference:
+ - Updated names and documentation path.
+ * debian/{liblinebreak1 -> liblinebreak2}.install:
+ - Updated for new upstream release.
+ * debian/liblinebreak1.symbols:
+ - Removed.
+ * debian/liblinbreak2.symbols:
+ - Created.
+
+ -- Eugene V. Lyubimkin <jackyf at debian.org> Fri, 08 Apr 2011 20:56:44 +0300
+
+liblinebreak (1.2-1) unstable; urgency=low
+
+ * New upstream release.
+ * debian/control:
+ - Bumped 'Standards-Version' to 3.8.1, no changes needed.
+ - Added 'autotools-dev' to Build-Depends for newer config.sub and
+ config.guess files.
+ * debian/rules:
+ - Copy newer config.sub and config.guess files for build stage and revert
+ them back in clean target.
+ * debian/liblinebreak1.install:
+ - Adapted to new upstream release.
+ * debian/liblinebreak1.symbols:
+ - Updated.
+
+ -- Eugene V. Lyubimkin <jackyf.devel at gmail.com> Sun, 03 May 2009 11:00:26 +0300
+
+liblinebreak (1.0-3) unstable; urgency=low
+
+ * debian/watch:
+ - Upstream has now placed upstream tarball, so filled it up.
+
+ -- Eugene V. Lyubimkin <jackyf.devel at gmail.com> Thu, 29 Jan 2009 20:36:15 +0200
+
+liblinebreak (1.0-2) experimental; urgency=low
+
+ * debian/liblinebreak1.symbols:
+ - Added.
+ * debian/control:
+ - Removed duplicated 'Section' line from liblinebreak1 entry.
+
+ -- Eugene V. Lyubimkin <jackyf.devel at gmail.com> Sat, 24 Jan 2009 10:52:16 +0200
+
+liblinebreak (1.0-1) experimental; urgency=low
+
+ * New upstream release.
+ * debian/control:
+ - Reworked, added shared library package (liblinebreak1) and documentation
+ package (liblinebreak-doc).
+ - Set DM-Upload-Allowed flag.
+ * debian/rules:
+ - Reworked according to new upstream release.
+ - Removed some unneeded cruft.
+ * debian/liblinebreak-doc.install:
+ - Added with path for documentation.
+ * debian/*.install:
+ - Reworked.
+ * debian/README.Debian:
+ - Removed as obsolete.
+ * debian/NEWS:
+ - Added with notion about static library.
+ * debian/liblinebreak-doc.doc-base.reference:
+ - Added.
+
+ -- Eugene V. Lyubimkin <jackyf.devel at gmail.com> Sun, 11 Jan 2009 11:11:21 +0200
+
+liblinebreak (0.9.6-6) unstable; urgency=low
+
+ * debian/rules:
+ - Removed empty 'clean' and 'binary-indep', lintian became more clever.
+ - Fixed mistake leading to double-building the package.
+ - Added support for 'noopt' in DEB_BUILD_OPTIONS.
+ - Library now builds with '-D_REENTRANT' flag.
+ * debian/control:
+ - Bumped 'Standards-Version' to 3.8.0.
+ * debian/watch:
+ - Added (comments only).
+
+ -- Eugene V. Lyubimkin <jackyf.devel at gmail.com> Sun, 13 Jul 2008 22:00:06 +0300
+
+liblinebreak (0.9.6-5) unstable; urgency=low
+
+ * New maintainer. (Closes: #483258)
+ * debian/control:
+ - Updated 'Maintainer' field.
+ - Removed 'Vcs-Git' field.
+ * debian/rules:
+ - Added 'clean' and 'binary-indep' rules to satisfy lintian.
+
+ -- Eugene V. Lyubimkin <jackyf.devel at gmail.com> Fri, 30 May 2008 00:59:40 +0300
+
+liblinebreak (0.9.6-4) unstable; urgency=low
+
+ * Orphaned the package.
+ * debhelper v7; rules file minimisation.
+
+ -- Joey Hess <joeyh at debian.org> Tue, 27 May 2008 19:28:39 -0400
+
+liblinebreak (0.9.6-3) unstable; urgency=low
+
+ * Build the library -fPIC so that it can be linked into libzltext.
+
+ -- Joey Hess <joeyh at debian.org> Tue, 08 Apr 2008 19:48:56 -0400
+
+liblinebreak (0.9.6-2) unstable; urgency=low
+
+ * First upload to debian.
+
+ -- Joey Hess <joeyh at debian.org> Sat, 22 Mar 2008 19:21:02 -0400
+
+liblinebreak (0.9.6-1) stable; urgency=low
+
+ * New upstream version.
+
+ -- Nikolay Pultsin <geometer at fbreader.org> Wed, 19 Mar 2008 15:52:00 +0300
+
+liblinebreak (0.9-1) stable; urgency=low
+
+ * Initial release.
+
+ -- Nikolay Pultsin <geometer at fbreader.org> Sun, 9 Mar 2008 03:19:00 +0300
diff --git a/debian/compat b/debian/compat
new file mode 100644
index 0000000..f599e28
--- /dev/null
+++ b/debian/compat
@@ -0,0 +1 @@
+10
diff --git a/debian/control b/debian/control
new file mode 100644
index 0000000..919478f
--- /dev/null
+++ b/debian/control
@@ -0,0 +1,39 @@
+Source: libunibreak
+Section: text
+Priority: optional
+Maintainer: Eugene V. Lyubimkin <jackyf at debian.org>
+Standards-Version: 3.9.6
+Build-Depends: debhelper (>= 7.2.11), dh-autoreconf
+
+Package: libunibreak-dev
+Section: libdevel
+Architecture: any
+Depends: ${misc:Depends}, libunibreak5 (= ${binary:Version})
+Conflicts: liblinebreak-dev, liblinebreak2-dev
+Suggests: libunibreak-doc (>= ${source:Version})
+Description: line breaking library for Unicode (development files)
+ libunibreak is an implementation of the Unicode line breaking algorithm
+ described at http://www.unicode.org/reports/tr29/tr29-21.html
+ .
+ This package contains development header files.
+
+Package: libunibreak5
+Architecture: any
+Depends: ${misc:Depends}, ${shlibs:Depends}
+Replaces: libunibreak1
+Description: line breaking library for Unicode (shared library)
+ libunibreak is an implementation of the Unicode line breaking algorithm
+ described at http://www.unicode.org/reports/tr29/tr29-21.html
+ .
+ This package contains shared library to dynamically link with.
+
+Package: libunibreak-doc
+Section: doc
+Architecture: all
+Depends: ${misc:Depends}
+Description: line breaking library for Unicode (documentation)
+ libunibreak is an implementation of the Unicode line breaking algorithm
+ described at http://www.unicode.org/reports/tr29/tr29-21.html
+ .
+ This package contains documentation.
+
diff --git a/debian/copyright b/debian/copyright
new file mode 100644
index 0000000..6e5cc57
--- /dev/null
+++ b/debian/copyright
@@ -0,0 +1,90 @@
+Sources were downloaded from:
+
+ http://downloads.sourceforge.net/vimgadgets
+
+Authors:
+ Wu Yongwei, Nikolay Pultsin, Thomas Klausner, Tom Hacohen.
+
+Files: *
+Copyright: (C) 2008-2012 Wu Yongwei <wuyongwei at gmail dot com>
+Copyright: (C) 2012-2013 Tom Hacohen <tom at stosb.com>
+License: other
+ /*
+ * This software is provided 'as-is', without any express or implied
+ * warranty. In no event will the author be held liable for any damages
+ * arising from the use of this software.
+ *
+ * Permission is granted to anyone to use this software for any purpose,
+ * including commercial applications, and to alter it and redistribute
+ * it freely, subject to the following restrictions:
+ *
+ * 1. The origin of this software must not be misrepresented; you must
+ * not claim that you wrote the original software. If you use this
+ * software in a product, an acknowledgement in the product
+ * documentation would be appreciated but is not required.
+ * 2. Altered source versions must be plainly marked as such, and must
+ * not be misrepresented as being the original software.
+ * 3. This notice may not be removed or altered from any source
+ * distribution.
+ *
+ * [...]
+ *
+ * The Unicode Terms of Use are available at
+ * <URL:http://www.unicode.org/copyright.html>
+ */
+
+Files: linebreakdata.c, wordbreakdata.c
+Copyright: (c) 1991-2013 Unicode, Inc.
+License: other
+ http://www.unicode.org/terms_of_use.html
+ .
+ EXHIBIT 1
+ UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE
+ .
+ Unicode Data Files include all data files under the directories
+ http://www.unicode.org/Public/, http://www.unicode.org/reports/, and
+ http://www.unicode.org/cldr/data/ . Unicode Software includes any source
+ codep ublished in the Unicode Standard or under the directories
+ http://www.unicode.org/Public/, http://www.unicode.org/reports/, and
+ http://www.unicode.org/cldr/data/.
+ .
+ NOTICE TO USER: Carefully read the following legal agreement. BY
+ DOWNLOADING, INSTALLING, COPYING OR OTHERWISE USING UNICODE INC.'S DATA FILES
+ ("DATA FILES"), AND/OR SOFTWARE ("SOFTWARE"), YOU UNEQUIVOCALLY ACCEPT, AND
+ AGREE TO BE BOUND BY, ALL OF THE TERMS AND CONDITIONS OF THIS AGREEMENT. IF
+ YOU DO NOT AGREE, DO NOT DOWNLOAD, INSTALL, COPY, DISTRIBUTE OR USE THE DATA
+ FILES OR SOFTWARE.
+ .
+ COPYRIGHT AND PERMISSION NOTICE
+ .
+ Copyright (c) 1991-2013 Unicode, Inc. All rights reserved. Distributed
+ under the Terms of Use in http://www.unicode.org/copyright.html.
+ .
+ Permission is hereby granted, free of charge, to any person obtaining a
+ copy of the Unicode data files and any associated documentation (the "Data
+ Files") or Unicode software and any associated documentation (the "Software")
+ to deal in the Data Files or Software without restriction, including without
+ limitation the rights to use, copy, modify, merge, publish, distribute, and/or
+ sell copies of the Data Files or Software, and to permit persons to whom the
+ Data Files or Software are furnished to do so, provided that (a) the above
+ copyright notice(s) and this permission notice appear with all copies of the
+ Data Files or Software, (b) both the above copyright notice(s) and this
+ permission notice appear in associated documentation, and (c) there is clear
+ notice in each modified Data File or in the Software as well as in the
+ documentation associated with the Data File(s) or Software that the data or
+ software has been modified.
+ .
+ THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY
+ KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD
+ PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN
+ THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL
+ DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
+ WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
+ OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE DATA FILES OR
+ SOFTWARE.
+ .
+ Except as contained in this notice, the name of a copyright holder shall
+ not be used in advertising or otherwise to promote the sale, use or other
+ dealings in these Data Files or Software without prior written authorization of
+ the copyright holder.
diff --git a/debian/libunibreak-dev.install b/debian/libunibreak-dev.install
new file mode 100644
index 0000000..961c762
--- /dev/null
+++ b/debian/libunibreak-dev.install
@@ -0,0 +1,3 @@
+usr/include/* usr/include/
+usr/lib/*/libunibreak.so
+usr/lib/*/pkgconfig/
diff --git a/debian/libunibreak-doc.install b/debian/libunibreak-doc.install
new file mode 100644
index 0000000..e69de29
diff --git a/debian/libunibreak5.install b/debian/libunibreak5.install
new file mode 100644
index 0000000..a45f4a3
--- /dev/null
+++ b/debian/libunibreak5.install
@@ -0,0 +1 @@
+usr/lib/*/libunibreak.so.*
diff --git a/debian/rules b/debian/rules
new file mode 100755
index 0000000..1aa0839
--- /dev/null
+++ b/debian/rules
@@ -0,0 +1,13 @@
+#!/usr/bin/make -f
+
+DPKG_EXPORT_BUILDFLAGS = 1
+-include /usr/share/dpkg/buildflags.mk
+
+%:
+ dh $@ --with autoreconf
+
+override_dh_auto_configure:
+ dh_auto_configure -- --disable-static
+
+override_dh_auto_build:
+ make -- doc
diff --git a/debian/watch b/debian/watch
new file mode 100644
index 0000000..948b027
--- /dev/null
+++ b/debian/watch
@@ -0,0 +1,3 @@
+version=4
+opts=filenamemangle=s/.+\/?(\d\S+)\.tar\.gz/libunibreak-$1\.tar\.gz/ \
+ https://github.com/adah1972/libunibreak/tags .*/?(\d\S+)\.tar\.gz
More information about the Neon-commits
mailing list