From: balejk <balejk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Package request: sstp-client
Date: Tue, 17 Oct 2023 19:43:01 +0200 [thread overview]
Message-ID: <20231017174301.sy9eRRwpWxMn6kbt3KaINnBwRbeN-DQgtAyMc7T6__Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46669@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
New comment by balejk on void-packages repository
https://github.com/void-linux/void-packages/issues/46669#issuecomment-1766880793
Comment:
I have written a template for this some time ago, feel free to use it:
```
# Template file for 'sstp-client'
pkgname=sstp-client
version=1.0.19
revision=1
build_style=gnu-configure
configure_script=./autogen.sh
hostmakedepends="pkg-config autoconf automake libtool"
makedepends="libevent-devel ppp-devel libtls-devel"
short_desc="A client implementation of Secure Socket Tunneling Protocol (SSTP)"
maintainer=
license="GPL-3.0-or-later"
homepage="https://gitlab.com/eivnaes/sstp-client"
distfiles="https://gitlab.com/eivnaes/sstp-client/-/archive/${version}/sstp-client-${version}.tar.gz"
checksum=e2652365f69f5037102e78f4e115ff764a390b27bb3fd513a8a50b10a61bb613
```
However, I have been having some issues with the latest version (you can take a look at the project's issue tracker at Gitlab) so right now I'm running a git version. If you happen to run into the same problems, you can just change the template to use version 1.0.18 for now (don't forget to update the checksum), however please note that 1.0.18 requires a simple patch in order to be compilable on musl (see the project's git log, something like second commit after the 1.0.18 tag).
next prev parent reply other threads:[~2023-10-17 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 22:00 [ISSUE] " michalszmidt
2023-10-17 17:43 ` balejk [this message]
2023-12-19 2:45 ` [ISSUE] [CLOSED] " sgn
2023-12-29 16:50 ` michalszmidt
2023-12-29 18:09 ` balejk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231017174301.sy9eRRwpWxMn6kbt3KaINnBwRbeN-DQgtAyMc7T6__Q@z \
--to=balejk@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).