From: Heavenly Avenger <avenger@avenger.ws>
To: cygwin-apps@cygwin.com
Subject: libssh2 1.8.0, 1.8.1-20181201(test)
Date: Sat, 01 Dec 2018 22:49:00 -0000 [thread overview]
Message-ID: <fc18a8a6-df7a-d123-75ef-2e576ca39b3a@avenger.ws> (raw)
Hello!
The libssh2 (www.libssh2.org) package is way out of date in cygwin repo
and no test/unstable available. I was frustrated with this and went down
the trouble to build it myself.
I can't commit to become a permanent package maintainer but I'm sharing
with you the cygport and package files in case somebody wants to update
the official cygwin repositories.
I have built two package sets: libssh2-1.8.0 (which includes the same
1.7.0's _1 and -devel subsets) and also libssh2-1.8.1-20181201 off
latest daily from libssh.org. I needed public key compatibility with
modern OpenSSH implementations, which was also absent from the 1.8.0
release.
The cygport files for both package sets is at:
https://avenger.ws/cygwin/cygport.
I built the packages and, in an attempt to follow the packages
contribution guide
(https://cygwin.com/packaging-contributors-guide.html), also am
providing them here:
https://avenger.ws/cygwin/x86_64/libssh2/
I have manually added "test:" lines to 1.8.1-20181201 with the following
script, because I believe this is the only way to tag packages as
test/unstable:
----
#!/bin/bash
echo -n "Appending 'test:' to hint files: "
for hintfile in $(find */dist -name '*.hint' -type f); do
 if [ -z "$(egrep "^test:" "${hintfile}")" ]; then
 echo -n "."
 echo "test:" >> "${hintfile}"
 else
 echo -n ","
 fi
done
echo " done."
----
I just run this right after assembling the unstable package. As for what
I could find in the mailing list archives, this is a manual process, and
as the thread I found about it was somewhat recent (2017), I believe
this is still not something supported in the cygport files. The test
version is built with libssh2's debugging trace() enabled.
Hope this is a welcome contribution for the cygwin community!
p.s.: maybe libssh2 still has a maintainer around, so just letting them
know, I could build it without any patch, so it should be easy to update.
next reply other threads:[~2018-12-01 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-01 22:49 Heavenly Avenger [this message]
2018-12-01 23:17 ` Ken Brown
2018-12-02 0:03 ` Heavenly Avenger
2018-12-02 15:09 ` cyg Simple
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=fc18a8a6-df7a-d123-75ef-2e576ca39b3a@avenger.ws \
--to=avenger@avenger.ws \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).