On Wed, 2009-12-02 at 09:57 +0100, Tomáš Chvátal wrote:
> Dne středa 02 Prosinec 2009 09:51:25 Christian Faulhammer napsal(a):
> > At the moment I don't remember for what reason exactly, but we renamed
> > the PATCHES variable to EBZR_PATCHES in bzr.eclass. You should do
> > something similar.
>
On Wed, 2009-12-02 at 11:46 +0100, Fabian Groffen wrote:
> I guess you better add a section for known eapis that are too old to
> your liking, and use the *) section for an oops message saying you don't
> know about ${EAPI} yet, and to please file a bug.
Yes, good idea. We've gone with this solut
Hi,
Tomáš Chvátal :
> > The sense of this I don't understand. You should not restrict EAPI
> > like this.
> >
> > V-Li
> >
> Why not. Quite standart way.
> 19 case ${EAPI:-0} in
> 20 2) : ;;
> 21 *) DEPEND="EAPI-TOO-OLD" ;;
> 22 esac
Microsoft Windows is standard software, too
On 02-12-2009 09:57:37 +0100, Tomáš Chvátal wrote:
> Dne středa 02 Prosinec 2009 09:51:25 Christian Faulhammer napsal(a):
> > At the moment I don't remember for what reason exactly, but we renamed
> > the PATCHES variable to EBZR_PATCHES in bzr.eclass. You should do
> > something similar.
> No re
Dne středa 02 Prosinec 2009 09:51:25 Christian Faulhammer napsal(a):
> At the moment I don't remember for what reason exactly, but we renamed
> the PATCHES variable to EBZR_PATCHES in bzr.eclass. You should do
> something similar.
No reason to rename it if they use base_src_prepare
>
> EXPORT_FU
Hans de Graaff :
> The eclass itself is attached to this message and here:
> http://git.overlays.gentoo.org/gitweb/?p=proj/ruby-scripts.git;a=blob;f=ruby-ng-testbed/eclass/ruby-ng.eclass;h=ce9a37440600c7913a21b5780a18b5e8dd9d712f;hb=HEAD
At the moment I don't remember for what reason exactly, bu
