Date: Wed, 03 Sep 2014 23:35:44 +0200 From: Matthias Andree <matthias.andree@gmx.de> To: freebsd-ports@freebsd.org Subject: Re: [BRAINSTORMING] simplifying maintainer's life Message-ID: <540789B0.5040808@gmx.de> In-Reply-To: <20140903145614.158f8e89@kalimero.tijl.coosemans.org> References: <20140903082538.GE63085@ivaldir.etoilebsd.net> <20140903145614.158f8e89@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 03.09.2014 um 14:56 schrieb Tijl Coosemans: > 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. > > Another idea is to support shell glob patterns (*?[) in pkg-plist. This > 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-plists > are just too long or too complicated depending on options. That is a bad idea. We have scripts to generate the pkg-plist to stdout, and something like make makeplist >/tmp/plist.new vim -o pkg-plist /tmp/plist.new works like a breeze for me, meaning it is very easy to maintain the list. With graphical editors that show two files at the same time, or with mouse support in vim, it's even easier to copy and paste entire blocks, for instance, from auto-generated HTML documentation. There is no reason to facilitate throwing away robustness and stability of the package build and listen to complaints about missing files.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?540789B0.5040808>