diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-28 09:55:11 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-28 09:55:11 +0000 |
commit | cd07912073c951b4bbb871ed2653af1be2cfc714 (patch) | |
tree | 1073c2308492e6aea4c66cb7436ee92db2abfd42 /distro/pkg/deb/README.Debian | |
parent | Initial commit. (diff) | |
download | libyang2-cd07912073c951b4bbb871ed2653af1be2cfc714.tar.xz libyang2-cd07912073c951b4bbb871ed2653af1be2cfc714.zip |
Adding upstream version 2.1.30.upstream/2.1.30upstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to '')
-rw-r--r-- | distro/pkg/deb/README.Debian | 38 |
1 files changed, 38 insertions, 0 deletions
diff --git a/distro/pkg/deb/README.Debian b/distro/pkg/deb/README.Debian new file mode 100644 index 0000000..fc680d0 --- /dev/null +++ b/distro/pkg/deb/README.Debian @@ -0,0 +1,38 @@ +Debian packaging for libyang +============================ + +Where to file issues +-------------------- + +Please file issues on the Debian BTS as usual. You could also open issues +on github, but if it's something about the Debian packaging it's better to +stick with the proper Debian ways. The Debian BTS is where other people +involved with Debian go look for bugs regarding a package, so that's where +they should be. + +Building straight off git +------------------------- + +Just the normal: + +``` +git clone https://github.com/CESNET/libyang -b debian/master +cd libyang +dpkg-buildpackage +``` + +Building a Debian .dsc +---------------------- + +Again, pretty much the normal: + +``` +git clone https://github.com/CESNET/libyang -b debian/master +wget -Olibyang_0.16.105.orig.tar.gz https://github.com/CESNET/libyang/archive/v0.16-r3.tar.gz +cd libyang +dpkg-source -b . +``` + +(Note the diverging release numbering though.) + + -- Ondřej Surý <Ondřej Surý <ondrej@debian.org>>, Fri, 22 May 2020 11:10:55 +0200 |