btw, Makefile didn't have whitespaces between all variables, but OK anyways.
2018-06-15 11:02 GMT-03:00 Elias M. Mariani <marianiel...@gmail.com>: > Makefile its OK. > Build OK. > Install OK. > The server and client works. > make port-lib-depends-check without errors. > > Can I give an OK ? > OK by me if that's the case. > > Cheers. > Elias. > > > 2018-06-14 17:00 GMT-03:00 Stuart Henderson <s...@spacehopper.org>: >> I'm not expecting many to be able to actually test this, but it >> does work. Does anyone have time to review it ports-wise at least >> please? OK to commit? >> >> Full message attached so you don't have to go digging for a 2-week >> old mail with the tgz. >> >> >> >> ---------- Mensaje reenviado ---------- >> From: Stuart Henderson <s...@spacehopper.org> >> To: ports <ports@openbsd.org> >> Cc: >> Bcc: >> Date: Sun, 3 Jun 2018 01:11:38 +0100 >> Subject: NEW: devel/libcoap >> Thought I'd have a play with some controllable lights so I put this >> port together. Some tests fail (it has some which want v4-mapped-in-v6) >> but the main thing I'm interested in at the moment is coap-client which >> works well enough. >> >> I had to use gnu libtool (I ran out of beer trying to get it to work >> with libtool in base, now I just have a bottle which says Henri Bardouin >> on it so I'm sending this while I can still type ;) so if anyone has >> ideas how to fix that they would be welcome. >> >> Anyway it works well enough, so.. ok to import? >> >> (see https://chebe.dreamwidth.org/tag/lights if you want to get it >> working with the Trådfri gateway, some of the older guides you might >> find don't show how to do the DTLS identity setup which newer >> firmware requires, I pieced it together then found that page, >> which would have saved a bit of time if I'd found it earlier :) >> >> >> ------ >> libcoap implements a lightweight application-protocol for devices that >> are constrained in their resources such as computing power, RF range, >> memory, bandwith, or network packet sizes. This protocol, CoAP was >> standardized in the IETF as RFC 7252. >> >> The library provides the core functionality for development of >> resource-efficient CoAP servers and clients, including resource >> observation and block-wise transfer. >> >> Example implementations show how these features can be used in >> applications: >> >> coap-client is a wget-like tool to generate simple requests for >> retrieval and modification of resources on a remote server. >> >> coap-server is a basic server application that illustrates various >> server-side features of libcoap. >> >> coap-rd implements a simple CoAP Resource Directory. >> ------ >>
