From owner-freebsd-ports@FreeBSD.ORG Fri Apr 11 09:17:06 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 282AE6E4; Fri, 11 Apr 2014 09:17:06 +0000 (UTC) Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A3321C5B; Fri, 11 Apr 2014 09:17:05 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id hi2so656634wib.11 for ; Fri, 11 Apr 2014 02:17:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=3G352wSXW9BdJFSQNwTfMXGbkFZYNDEx2yf0jzpbs64=; b=QUwwbmL+CP0Sc21yyZiu/dbU7DE8KylpAF2eeGpa20+cOgbwrlFA0jMZKo7B5h4ajx N5wSk0b2Dc8LPuuP3HJu4umGpzRUf7Oi0l4sjv9teDSQy+7w12wYmK2NMPiuRVGhQewU gdIEYJzNZxe/1/jj+YB+Z2PzWfvdfY56f3KmFSLN84qA+EaWeX+gM5lIR3raMkrVwhbP I9pTPxguqCY0eRqbc9N6fULnI17KO+y9iBFYhzWXosAFAMJKs/LuuCDL4Wk7ZbUAg3EL ZlJ6h/dxiEJYjs+k+M5EVlXEF78FHJTtt9oWdaC7tyWyf1/TmdF7czPt+Hn+kyiTmASR imxg== X-Received: by 10.180.77.129 with SMTP id s1mr2457308wiw.56.1397207823708; Fri, 11 Apr 2014 02:17:03 -0700 (PDT) Received: from ivaldir.etoilebsd.net ([2001:41d0:8:db4c::1]) by mx.google.com with ESMTPSA id mw3sm3295108wic.7.2014.04.11.02.17.01 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 11 Apr 2014 02:17:02 -0700 (PDT) Sender: Baptiste Daroussin Date: Fri, 11 Apr 2014 11:17:00 +0200 From: Baptiste Daroussin To: Dominic Fandrey Subject: Re: New port, what's next? Message-ID: <20140411091700.GF29301@ivaldir.etoilebsd.net> References: <5346D5AF.5070905@bsdforen.de> <20140410182839.GB29301@ivaldir.etoilebsd.net> <5346E4F9.8030205@marino.st> <20140410211439.GB37706@e-new.0x20.net> <5347B26D.4000508@bsdforen.de> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GV0iVqYguTV4Q9ER" Content-Disposition: inline In-Reply-To: <5347B26D.4000508@bsdforen.de> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: marino@freebsd.org, Lars Engels , freebsd-ports@freebsd.org, Helmut Schneider X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Apr 2014 09:17:06 -0000 --GV0iVqYguTV4Q9ER Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Apr 11, 2014 at 11:14:21AM +0200, Dominic Fandrey wrote: > On 10/04/2014 23:14, Lars Engels wrote: > > On Thu, Apr 10, 2014 at 08:37:45PM +0200, John Marino wrote: > >> On 4/10/2014 20:28, Baptiste Daroussin wrote: > >>> On Thu, Apr 10, 2014 at 07:32:31PM +0200, Dominic Fandrey wrote: > >>>> > >>>> On 10/04/2014 18:53, Helmut Schneider wrote: > >>>>> I created a new port, Typo3-LTS. The tgz contains > >>>>> > >>>>> - Makefile > >>>>> - distinfo > >>>>> - pkg-plist > >>>>> - pkg-descr > >>>>> - a diff from www/typo3 > >>>>> > >>>>> The file has ~150kB so I assume it's to big for a PR. > >>>> > >>>> I assume the bulk of that is the pkg-plist. The largest pkg-plist > >>>> in the ports tree is 4M. In my opinion huge plists should be dynamic= ally > >>>> generated, but in your case I'd just I'd just temp-host the file > >>>> somewhere and file a PR with a link and a checksum. > >>>> > >>> Autoplist are harmful! and should be avoided as much as possible, I k= now python > >>> and ruby has it but I m really not happy about that > >>> > >>> autoplist is dangerous because we have no way to control that what is= package is > >>> what the maintainer expect to be packaged! therefore we often end up = with > >>> unoticed problems > >> > >> Yes, but 6,000 - 20,000 line plists are unwieldy to say the least. > >> And the danger can be mitigated by the maintainer by reviewing the > >> internal temporary package list, ideally on multiple platforms. Also > >> some plists are really hard to make manually if there are many options > >> or if the plist morphs depending on the combination of options. > >> > >> yes, a safety net is removed with a generated plist but it has it's > >> place. The maintainer just has to be vigilant. > >> > >=20 > > Can't we teach the ports system to handle pkg-plist.gz? >=20 > That would be easy enough. The question is, can svn handle it? Nope :) regards, Bapt --GV0iVqYguTV4Q9ER Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlNHswwACgkQ8kTtMUmk6Ex25QCdGUFucKMp9duyNawzXl9N3P0J 9f8AnRtKoPEtZAtUOo25qYkvy2CHUjy+ =8zQF -----END PGP SIGNATURE----- --GV0iVqYguTV4Q9ER--