CMakeLists.txt: Don't append git version to upstream tarball which confuses PPA build recipe...

README.md: Updated Launchpad PPA links and other minor information...
debian/changelog: Cleaned up changelog to better accommodate daily build bot recipe...
version.txt: Bumped versioning...
parent 8a1f6023
......@@ -221,7 +221,7 @@ endif()
# Set filename...
set(CPACK_SOURCE_PACKAGE_FILE_NAME
"${CMAKE_PROJECT_NAME}-${CPACK_PACKAGE_VERSION_MAJOR}.${CPACK_PACKAGE_VERSION_MINOR}.${CPACK_PACKAGE_VERSION_PATCH}-git${VERSION_GIT_DATE}")
"${CMAKE_PROJECT_NAME}-${CPACK_PACKAGE_VERSION_MAJOR}.${CPACK_PACKAGE_VERSION_MINOR}.${CPACK_PACKAGE_VERSION_PATCH}")
# Don't include these files in the archive...
set(CPACK_SOURCE_IGNORE_FILES
......
# Pistache
[![N|Solid](http://pistache.io/assets/images/logo.png)](https://www.github.com/oktal/pistache)
[![Travis Build Status](https://travis-ci.org/oktal/pistache.svg?branch=master)](https://travis-ci.org/oktal/pistache)
......@@ -16,15 +18,18 @@ Pistache was originally created by Mathieu Stefani, but he is no longer actively
For those that prefer IRC over Slack, the rag-tag crew of maintainers idle in `#pistache` on Freenode. Please come and join us!
The [Launchpad Team](https://launchpad.net/~pistache+team) administers the daily and stable Ubuntu pre-compiled packages.
# Precompiled Packages
If you have no need to modify the Pistache source, you are strongly recommended to use precompiled packages for your distribution. This will save you time.
## Debian and Ubuntu
We have submitted a [Request for Packaging](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929593) downstream to Debian. Once Pistache has an official Debian package maintainer intimately familiar with the [Debian Policy Manual](https://www.debian.org/doc/debian-policy/), we can expect to eventually see Pistache available in Debian and all derivatives (e.g. Ubuntu and many others).
We have submitted a [Request for Packaging](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929593) downstream to Debian. Once we have an official Debian package maintainer intimately familiar with the [Debian Policy Manual](https://www.debian.org/doc/debian-policy/), we can expect to eventually see it become available in Debian and all derivatives (e.g. Ubuntu and many others).
But until then currently Pistache has partially compliant upstream Debianization. Our long term goal is to have our source package properly Debianized downstream by a Debian Policy Manual SME. In the mean time consider using our PPAs to avoid having to build from source.
### Supported Architectures
Currently Pistache is built and tested on a number of [architectures](https://wiki.debian.org/SupportedArchitectures). Some of these are suitable for desktop or server use and others for embedded environments. As of this writing we do not currently have any MIPS related packages that have been either built or tested.
Currently Pistache is built and tested on a number of [architectures](https://wiki.debian.org/SupportedArchitectures). Some of these are suitable for desktop or server use and others for embedded environments. As of this writing we do not currently have any MIPS related packages that have been either built or tested. The `ppc64el` builds are occasionally tested on POWER9 hardware, courtesy of IBM.
- amd64
- arm64
......@@ -33,27 +38,28 @@ Currently Pistache is built and tested on a number of [architectures](https://wi
- ppc64el
- s390x
### Ubuntu PPA (Stable)
Currently there is no stable release of Pistache published to the [stable](https://launchpad.net/%7Ekip/+archive/ubuntu/pistache) PPA. However, when that time comes, run the following to install a stable package:
### Ubuntu PPA (Unstable)
The project builds [daily unstable snapshots](https://launchpad.net/~pistache+team/+archive/ubuntu/unstable) in a separate unstable PPA. To use it, run the following:
```console
$ sudo add-apt-repository ppa:kip/pistache
$ sudo add-apt-repository ppa:pistache+team/unstable
$ sudo apt update
$ sudo apt install libpistache-dev
```
### Ubuntu PPA (Unstable)
To use [unstable](https://launchpad.net/%7Ekip/+archive/ubuntu/pistache-unstable) packages, run the following:
### Ubuntu PPA (Stable)
Currently there are no stable release of Pistache published into the [stable](https://launchpad.net/~pistache+team/+archive/ubuntu/stable) PPA. However, when that time comes, run the following to install a stable package:
```console
$ sudo add-apt-repository ppa:kip/pistache-unstable
$ sudo add-apt-repository ppa:pistache+team/stable
$ sudo apt update
$ sudo apt install libpistache-dev
```
## Use via pkg-config
If you would like to automatically have your project's build environment use the appropriate compiler and linker build flags necessary to use Pistache, [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/) can greatly simplify things. The `libpistache-dev` package includes a pkg-config manifest.
If you would like to automatically have your project's build environment use the appropriate compiler and linker build flags, [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/) can greatly simplify things. It is the portable international _de facto_ standard for determining build flags. The `libpistache-dev` package includes a pkg-config manifest.
To use with the GNU Autotools, as an example, include the following snippet in your project's `configure.ac`:
......@@ -61,8 +67,8 @@ To use with the GNU Autotools, as an example, include the following snippet in y
# Pistache...
PKG_CHECK_MODULES(
[libpistache], [libpistache >= 0.0], [],
[AC_MSG_ERROR([libpistache >= 0.0 missing...])])
[libpistache], [libpistache >= 0.0.2], [],
[AC_MSG_ERROR([libpistache >= 0.0.2 missing...])])
YOURPROJECT_CXXFLAGS="$YOURPROJECT_CXXFLAGS $libpistache_CFLAGS"
YOURPROJECT_LIBS="$YOURPROJECT_LIBS $libpistache_LIBS"
......@@ -141,6 +147,7 @@ struct HelloHandler : public Http::Handler {
};
int main() {
Http::listenAndServe<HelloHandler>("*:9080");
Http::listenAndServe<HelloHandler>(Pistache::Address("*:9080"));
}
```
pistache (0.0.002-git20200113-kip1) eoan; urgency=medium
pistache (0.0.002) eoan; urgency=medium
* Latest upstream.
* Fixed DEP-8 debian/test/test-compilation-and-link.sh
-- Kip Warner <kip@thevertigo.com> Mon, 13 Jan 2020 20:15:48 -0800
pistache (0.0.002-git20200111-kip1) eoan; urgency=medium
* Latest upstream.
-- Kip Warner <kip@thevertigo.com> Sat, 11 Jan 2020 14:04:54 -0800
pistache (0.0.001-git20200101-kip1) eoan; urgency=medium
* Latest upstream.
-- Kip Warner <kip@thevertigo.com> Tue, 31 Dec 2019 20:21:00 -0800
pistache (0.0.001-git20191031-kip1) eoan; urgency=medium
* Latest upstream and first build for eoan.
-- Kip Warner <kip@thevertigo.com> Thu, 31 Oct 2019 18:23:04 -0700
pistache (0.0.001-git20191017-kip1) disco; urgency=medium
* Latest upstream.
-- Kip Warner <kip@thevertigo.com> Thu, 17 Oct 2019 21:57:28 -0700
pistache (0.0.001-git20190920-kip1~disco) disco; urgency=medium
* Added DEP-8 compliant test for autopkgtest.
-- Kip Warner <kip@thevertigo.com> Fri, 20 Sep 2019 15:23:06 -0700
-- Kip Warner <kip@thevertigo.com> Fri, 17 Jan 2020 14:29:59 -0800
VERSION_MAJOR 0
VERSION_MINOR 0
VERSION_PATCH 002
VERSION_GIT_DATE 20200113
VERSION_GIT_DATE 20200117
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment