From owner-freebsd-ports@FreeBSD.ORG Tue Jun 3 12:44:12 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CDEF2A47 for ; Tue, 3 Jun 2014 12:44:12 +0000 (UTC) Received: from relay.andxor.it (relay.andxor.it [78.134.40.50]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1EF13253C for ; Tue, 3 Jun 2014 12:44:10 +0000 (UTC) Received: (qmail 45370 invoked from network); 3 Jun 2014 12:44:08 -0000 Received: from alex.andxor.it (a.premoli@andxor.it@192.168.2.30) by relay.andxor.it with ESMTPSA; 3 Jun 2014 12:44:08 -0000 Message-ID: <538DC318.6020401@FreeBSD.org> Date: Tue, 03 Jun 2014 14:44:08 +0200 From: Alex Dupre User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26 MIME-Version: 1.0 To: Stefan Bethke , Freebsd_mailinglist_PORTS , gslin@gslin.org Subject: Re: roundcube's switch to composer, anything plugin port maintainers should be doing? References: <6A929127-2407-4A18-AD8F-42A1B261B83A@lassitu.de> In-Reply-To: <6A929127-2407-4A18-AD8F-42A1B261B83A@lassitu.de> X-Enigmail-Version: 1.6.1_pre20140112 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit 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 12:44:12 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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’ve 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… 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. - -- Alex Dupre -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) Comment: Using GnuPG with SeaMonkey - http://www.enigmail.net/ iEYEARECAAYFAlONwxgACgkQgRXp2M5fVU3XswCeLKaMnh4M+nh8FbEdFkjMp5Ny 0FwAn39S9AuaBzzezAE4XY3TAtoUSAJ7 =YSZ5 -----END PGP SIGNATURE-----