Date: Wed, 11 May 2011 11:15:59 +0200 From: Matthias Andree <mandree@FreeBSD.org> To: FreeBSD-gnats-submit@FreeBSD.org Cc: dinoex@FreeBSD.org, miwi@FreeBSD.org, wen@FreeBSD.org, lx@FreeBSD.org, sunpoet@FreeBSD.org, clsung@FreeBSD.org Subject: ports/156954: archivers/lzo to be deprecated and expired Message-ID: <E1QK5WS-000A8G-03@apollo.emma.line.org> Resent-Message-ID: <201105110920.p4B9K7ud084949@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 156954 >Category: ports >Synopsis: archivers/lzo to be deprecated and expired >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed May 11 09:20:07 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Matthias Andree >Release: FreeBSD 8.2-RELEASE amd64 >Organization: >Environment: System: FreeBSD apollo.emma.line.org 8.2-RELEASE FreeBSD 8.2-RELEASE #65: Fri Feb 25 01:47:50 CET 2011 toor@apollo.emma.line.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Dear fellows, Six years after the release of lzo-2.00, I'd like to discontinue the lzo-1.08 port, it has been obsolete since six years. The required upstream changes are minor, and I hope most upstreams have measures in place that their code supports lzo 2.00+ right out of the box. The number of direct dependencies, according the the INDEX, is rather concise, and given below, sorted by maintainer: clsung: archivers/p5-Compress-LZO and archivers/p5-POE-Filter-LZO dinoex: security/tinc lx: security/silktools miwi: archivers/dact sunpoet: archivers/p5-IO-Compress-Lzop wen: devel/py-tables Can I ask you to check if your port can be built with lzo2? Unless I hear objections, I'll remove lzo-1 end of May 2011. See archivers/lzop or security/openvpn for examples how to deal with the default version to be picked up. This is taken from LZO 2's changelog: <http://www.oberhumer.com/opensource/lzo/lzonews.php>; (between 2.00 and 1.08) Upgrade instructions from LZO v1 to LZO v2: * On 64-bit architectures, revisit all uses of lzo_uint. * Adapt for the maximum expansion change of incompressible data. * If you use the progress callback then adapt for the new interface. * Use #include <lzo/lzoXXX.h> or adjust your include path. * Check your code for use of deprecated macros. Add a #define LZO_CFG_COMPAT if necessary. * Other than that LZO v2 should be fully source-compatible with LZO v1. Of course, the compressed data is fully compatible as well. * Re-compile and re-link your application. * Enjoy the improvements! More details in the lzo 2.00 changelog entry. Thank you! >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1QK5WS-000A8G-03>