mifr/subsurface
1
0
Fork 0
mirror of https://github.com/subsurface/subsurface.git synced 2025-02-02 12:13:24 +00:00
Code Issues Projects Releases Packages Wiki Activity
subsurface/packaging/ubuntu/debian/changelog

8 lines
224 B
Text
Raw Normal View History

build-system: add valid Ubuntu/Debian changelog file We don't want to try to track every change to this file in our source repo, so this starting point is as goos as any. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-04-18 14:39:20 -07:00
subsurface (4.9.3-1~xenial) xenial; urgency=medium
Add Ubuntu packaging instructions These files knowingly (one might say, intentionally) violate the spirit and letter of the Debian / Ubuntu packaging rules. They are intended to be able to create our own packages that include their own libdivecomputer, libgit2 and (later) libmarble. Especially for daily builds this is WAY easier than fighting with whatever may be the current version of these packages in Ubuntu (especially since this allows us to use our private libdivecomputer branch). This assumes that the user runs the make-package.sh script from a directory below which we have subsurface/ <- Subsurface checked out git tree subsurface/libdivecomputer <- desired libdivecomputer sources subsurface/libgit2 <- desired libgit2 source Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2014-12-01 16:00:47 -08:00
build-system: add valid Ubuntu/Debian changelog file We don't want to try to track every change to this file in our source repo, so this starting point is as goos as any. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-04-18 14:39:20 -07:00
* Next release build - please check https://subsurface-
divelog.org/category/news/ for details
-- Dirk Hohndel <dirk@hohndel.org> Sun, 08 Sep 2019 23:45:38 -0700
Add Ubuntu packaging instructions These files knowingly (one might say, intentionally) violate the spirit and letter of the Debian / Ubuntu packaging rules. They are intended to be able to create our own packages that include their own libdivecomputer, libgit2 and (later) libmarble. Especially for daily builds this is WAY easier than fighting with whatever may be the current version of these packages in Ubuntu (especially since this allows us to use our private libdivecomputer branch). This assumes that the user runs the make-package.sh script from a directory below which we have subsurface/ <- Subsurface checked out git tree subsurface/libdivecomputer <- desired libdivecomputer sources subsurface/libgit2 <- desired libgit2 source Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2014-12-01 16:00:47 -08:00
Reference in a new issue Copy permalink