From owner-freebsd-ports@FreeBSD.ORG Tue Jun 3 13:16:22 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA6588D7; Tue, 3 Jun 2014 13:16:22 +0000 (UTC) Received: from gilb.zs64.net (gilb.zs64.net [212.12.50.234]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "gilb.zs64.net", Issuer "Cryptonomicore CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 83F4E28C4; Tue, 3 Jun 2014 13:16:22 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id B4BA810CDE7; Tue, 3 Jun 2014 13:16:12 +0000 (UTC) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: roundcube's switch to composer, anything plugin port maintainers should be doing? From: Stefan Bethke In-Reply-To: <538DC318.6020401@FreeBSD.org> Date: Tue, 3 Jun 2014 15:17:02 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: <57C5C296-C3FC-4031-980F-65507D44A7FF@lassitu.de> References: <6A929127-2407-4A18-AD8F-42A1B261B83A@lassitu.de> <538DC318.6020401@FreeBSD.org> To: Alex Dupre X-Mailer: Apple Mail (2.1878.2) Cc: gslin@gslin.org, Freebsd_mailinglist_PORTS X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jun 2014 13:16:23 -0000 Am 03.06.2014 um 14:44 schrieb Alex Dupre : > Signierter PGP Teil > Stefan Bethke ha scritto: > > I was in the process of upgrading a roundcube plugin (sauserprefs) > > and noticed that roundcube is switching/has swichted to composer. > > This is the first time I=92ve come across composer. Should I ignore > > that for the moment? Is there work underway to convert the plugin > > ports to use composer? Should the plugin ports be removed in favor > > of using composer manually? Is composer production ready yet? > > > > Inquiring minds want to know=85 >=20 > Hi Stefan, like you this is the first time I've come across > 'composer'. It's a dependency manager, I have no plans to support it, > you can ignore it for the moment. The problem seems to be that plugin authors are moving to the new plugin = repository, which is based around Composer. The original download link = for sauserprefs is already gone. Unfortunately, for sauserprefs, there's only a snapshot version tagged = (as I understand it), and the old version numbers for the plugin seem to = have been abandoned. I could start doing dated snapshots from the plugins site on my own = mirror, but this doesn't seem it's the right thing to do. I ll get in touch with my plugin's author to see what his take is on the = situation. Stefan --=20 Stefan Bethke Fon +49 151 14070811