From owner-freebsd-ports@freebsd.org Thu Apr 5 20:38:39 2018 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63228FA125F for ; Thu, 5 Apr 2018 20:38:39 +0000 (UTC) (envelope-from peo@nethead.se) Received: from ns1.nethead.se (ns1.nethead.se [5.150.237.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns1.nethead.se", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E8087704E9 for ; Thu, 5 Apr 2018 20:38:38 +0000 (UTC) (envelope-from peo@nethead.se) X-Virus-Scanned: amavisd-new at Nethead AB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nethead.se; s=NETHEADSE; t=1522960716; bh=y1CXhBq2E0Tj4W6VwGBA/Ia8pfMxtuHyDAB4S9EpXHs=; h=Subject:To:References:From:Date:In-Reply-To; b=MMZ0afs58ih2/2Do/I3C0iS4CnwCNAlXvjCJKzB7BlgNji7ZuFAmFlGze9D8rrgii WuCm0BU4WRsyskNJG1LD7Z9ZYzilQ5ROImrEXhvzE8x/by2K/QoR3I4jVrHOAciGd4 E7FJHqRLgNoI5GN//umItLaMgqybaUJBChTtygx0= Subject: Re: phpLDAPadmin -- is it time to drop this from ports? To: freebsd-ports@freebsd.org References: <20180405143540.Horde.eh0M417d9DmLg6vslXFsDsm@webmail.nethead.se> <5158b0ca-eba3-b084-4af2-aa44316ca54c@FreeBSD.org> From: Per olof Ljungmark Message-ID: <5b253131-8a03-2fc8-ef81-860571622a7f@nethead.se> Date: Thu, 5 Apr 2018 22:38:33 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <5158b0ca-eba3-b084-4af2-aa44316ca54c@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Apr 2018 20:38:39 -0000 On 04/05/18 15:30, Matthew Seaman wrote: > On 05/04/2018 13:35, Per olof Ljungmark wrote: >> >> Quoting Matthew Seaman : >> >>> Dear all, >>> >>> I've maintained the net/phpldapadmin port for _many_ years. >>> Unfortunately this project seems to have ceased development upstream. >>> There hasn't been a new release for more than 5 years, nor any sign >>> of life from the original developer over much the same timespan.  PLA >>> still just about works, but it is lacking in support for more recent >>> versions of PHP and generally sufferring from lack of love. >>> >>> I'm beginning to think that it is about time to take this port around >>> the back of the barn and administer the coup-de-grace.  There are >>> other graphical front-ends to LDAP directories available, such as >>> 'LDAP Account Manager' https://www.ldap-account-manager.org/lamcms/ >>> (in ports as sysutils/ldap-account-manager), so people won't be left >>> entirely out to dry. >>> >>> What do people think?  Is it time to deprecate and expire PLA, or is >>> there a diehard core of users for whom PLA will need to be ripped >>> from their cold, dead hands? >> >> One diehard here... hands still warm... >> >> Have tried ldap-account-manager but does not suit my need at all. >> Unless anyone has a better suggestion for a lightweight web-based >> utility I vote for it to stay. > > I have a vague recollection of a web-based LDAP front end written in > python, but I entirely failed to make any sort of proper note about what > it was called... > >> I did an install just a month ago on php71 so not sure about "lacking >> in support for more recent >> versions of PHP", do you have any specifics? > > Yes, sure.  PLA sufferred from the upstream deprecation of mcrypt within > PHP.  We've added local patches to work around the problem -- these have > been obtained "from the net", basically a corps of PLA users supporting > it in an ad-hoc fashion between themselves.  As the dropping of mcrypt > affected core functionality like *logging in*, you might think upstream > would patch the core distribution and make a new release fairly rapidly, > but there's absolutely no sign of that. > > Personally I'm fairly happy to leave PLA to hum along to itself for the > time being, but if future changes to PHP render it unusable, or if there > are nasty security bugs discovered and no fixes available, I'm going to > have to reconsider. Thank you for considering. I'll try to find out where this ad-hoc work was going on and who did it - don't think mcrypt is missed by many. I'm a little surprised I'm the only one answering here as well... //per