Gentoo Archives: gentoo-pms

From: Brian Harring <ferringb@×××××.com>
To: gentoo-pms@l.g.o
Cc: Ulrich Mueller <ulm@g.o>
Subject: Re: [gentoo-pms] [PATCH] How about a \ChangeWhenAddingAnEAPI marker?
Date: Sun, 06 May 2012 22:33:34
Message-Id: 20120506223328.GA8340@localhost
In Reply to: Re: [gentoo-pms] [PATCH] How about a \ChangeWhenAddingAnEAPI marker? by Ciaran McCreesh
On Sun, May 06, 2012 at 08:42:34PM +0100, Ciaran McCreesh wrote:
> On Sun, 6 May 2012 21:40:42 +0200 > Ulrich Mueller <ulm@g.o> wrote: > > > It's easy to miss some places that have to be updated when adding a > > > new EAPI. This hack fixes that. It works like this: > > > > > In pms.tex, at the top, we say > > > > > \CurrentEAPIIs{4} > > > > > Then everywhere where we have EAPI dependent content, we put > > > > > \ChangeWhenAddingAnEAPI{4} > > > > > which we can then grep for. Also, if you change the current EAPI, > > > and forget to change any of the markers, an error is produced. > > > > This looks a bit over-engineered to me. Wouldn't simple comments serve > > the same purpose? > > Comments don't force a failure when you forget about them. Being > self-validating makes it hard to screw up accidentally.
Seconded; in the sphinx version of pms I've been playing w/ I was planning on using similar functionality (including deprecation markers so we make damn sure we remove stuff in later eapi's). ~brian