Date: Wed, 3 Sep 2014 18:09:10 +0200 From: Baptiste Daroussin <bapt@FreeBSD.org> To: Tijl Coosemans <tijl@coosemans.org> Cc: ports@freebsd.org Subject: Re: [BRAINSTORMING] simplifying maintainer's life Message-ID: <20140903160908.GO63085@ivaldir.etoilebsd.net> In-Reply-To: <20140903165622.3bff54e0@kalimero.tijl.coosemans.org> References: <20140903082538.GE63085@ivaldir.etoilebsd.net> <20140903145614.158f8e89@kalimero.tijl.coosemans.org> <20140903135029.GK63085@ivaldir.etoilebsd.net> <20140903165622.3bff54e0@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--sGwo475CiIwWEjLI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Sep 03, 2014 at 04:56:22PM +0200, Tijl Coosemans wrote: > On Wed, 3 Sep 2014 15:50:30 +0200 Baptiste Daroussin <bapt@FreeBSD.org> w= rote: > > On Wed, Sep 03, 2014 at 02:56:14PM +0200, Tijl Coosemans wrote: > >> On Wed, 3 Sep 2014 10:25:39 +0200 Baptiste Daroussin <bapt@FreeBSD.org= > 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. Glob sounds nice but can lead to easy failures with files named with glob patterns like archivers/deco regards, Bapt --sGwo475CiIwWEjLI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlQHPSQACgkQ8kTtMUmk6Ez8igCeNNxgHvWBW9m5P+EUagSb1WDd PwcAoMF+raIQiZH7xMXA/LPD7tuStyD0 =6cXb -----END PGP SIGNATURE----- --sGwo475CiIwWEjLI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140903160908.GO63085>