From owner-freebsd-ports@FreeBSD.ORG Wed Sep 3 17:21:17 2014 Return-Path: Delivered-To: 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 5BA18B9B; Wed, 3 Sep 2014 17:21:17 +0000 (UTC) Received: from mailrelay006.isp.belgacom.be (mailrelay006.isp.belgacom.be [195.238.6.172]) by mx1.freebsd.org (Postfix) with ESMTP id BFB9C19AE; Wed, 3 Sep 2014 17:21:16 +0000 (UTC) X-Belgacom-Dynamic: yes X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AocGAPRMB1RR8Z/O/2dsb2JhbABZgw2BKtAbAYEMF3eEBAEFVh4FEAsOCgklDyoeBhMZiC0BvkUBF49NB4RMBZM4hlSCUIE2k2mDYzsvgk8BAQE Received: from 206.159-241-81.adsl-dyn.isp.belgacom.be (HELO kalimero.tijl.coosemans.org) ([81.241.159.206]) by relay.skynet.be with ESMTP; 03 Sep 2014 19:21:13 +0200 Received: from kalimero.tijl.coosemans.org (kalimero.tijl.coosemans.org [127.0.0.1]) by kalimero.tijl.coosemans.org (8.14.9/8.14.9) with ESMTP id s83HLCI6008691; Wed, 3 Sep 2014 19:21:13 +0200 (CEST) (envelope-from tijl@coosemans.org) Date: Wed, 3 Sep 2014 19:21:06 +0200 From: Tijl Coosemans To: Baptiste Daroussin Subject: Re: [BRAINSTORMING] simplifying maintainer's life Message-ID: <20140903192106.77fecfdf@kalimero.tijl.coosemans.org> In-Reply-To: <20140903160908.GO63085@ivaldir.etoilebsd.net> References: <20140903082538.GE63085@ivaldir.etoilebsd.net> <20140903145614.158f8e89@kalimero.tijl.coosemans.org> <20140903135029.GK63085@ivaldir.etoilebsd.net> <20140903165622.3bff54e0@kalimero.tijl.coosemans.org> <20140903160908.GO63085@ivaldir.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; boundary="Sig_/=4sw95FiELdDmRO33KMgcuA"; protocol="application/pgp-signature" Cc: ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Sep 2014 17:21:17 -0000 --Sig_/=4sw95FiELdDmRO33KMgcuA Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 3 Sep 2014 18:09:10 +0200 Baptiste Daroussin wro= te: > On Wed, Sep 03, 2014 at 04:56:22PM +0200, Tijl Coosemans wrote: >> On Wed, 3 Sep 2014 15:50:30 +0200 Baptiste Daroussin = wrote: >>> On Wed, Sep 03, 2014 at 02:56:14PM +0200, Tijl Coosemans wrote: >>>> On Wed, 3 Sep 2014 10:25:39 +0200 Baptiste Daroussin wrote: >>>>> On of the most borring thing IMHO in the plist maintainance is all the >>>>> directories. >>>>=20 >>>> Another idea is to support shell glob patterns (*?[) in pkg-plist. Th= is >>>> is possible now thanks to staging. It would allow moving PORTDOCS, >>>> PORTDATA and PORTEXAMPLES to pkg-plist. But more importantly, it would >>>> allow automatic plists that some ports create in post-install to be >>>> turned back into a real pkg-plist. Without glob patterns some pkg-pli= sts >>>> are just too long or too complicated depending on options. >>>=20 >>> We could also say pack everything that is in that stage directory. >>>=20 >>> The problem is right now I do like static plist because if something >>> fails to build for $reason, that the plist doesn't find a file in the >>> staging area and we notice quite quickly that something as failed. >>> with autoplist or globbing we do lose this feature and we need to way >>> deal with it. >>> In anycase we won't make full autoplist because we still need to be >>> able to specify credentials files per files if needed. But glob is >>> really appealing :) >>=20 >> I completely agree :) Files should be listed explicitly if possible, >> but sometimes it's very inconvenient and in these cases some ports >> roll their own autoplist implementations which worse than having a >> static pkg-plist with a few glob patterns. >>=20 >> Moving PORTDOCS etc. to pkg-plist means all package content is listed >> in one file. That will probably simplify check-plist too. >=20 > Glob sounds nice but can lead to easy failures with files named with > glob patterns like archivers/deco Hmm. Those characters would have to be escaped, just like on the command line. glob(3) already handles all of that though. --Sig_/=4sw95FiELdDmRO33KMgcuA Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREKAAYFAlQHTgcACgkQfoCS2CCgtislSAD+IkVPZjmVXImSHHtNMroL+0wW vIXF7hsqlpa6OO6WhGkBAIJ+if8qxb63p94nBp2yYEmn9luu6QQFUMfR9bnAxNIG =O6Vu -----END PGP SIGNATURE----- --Sig_/=4sw95FiELdDmRO33KMgcuA--