Skip site navigation (1)Skip section navigation (2)
Date:      11 Apr 2000 17:26:40 -0700
From:      asami@FreeBSD.org (Satoshi - Ports Wraith - Asami)
To:        "R. Imura" <imura@af.airnet.ne.jp>
Cc:        knu@idaemons.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   Re: cvs commit: ports/chinese Makefile.inc ports/german  Makefile.inc         ports/japanese Makefile.inc ports/korean  Makefile.inc         ports/russian Makefile.inc ports/vietnamese  Makefile.inc
Message-ID:  <vqcn1n0i2pr.fsf@silvia.hip.berkeley.edu>
In-Reply-To: "R. Imura"'s message of "Wed, 12 Apr 2000 08:36:21 %2B0900"
References:  <vqc4s99ox22.fsf@silvia.hip.berkeley.edu> <20000412005730F.imura@cs.titech.ac.jp> <86bt3gk2oi.wl@archon.local.idaemons.org> <20000412083621F.imura@cs.titech.ac.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
 * From: "R. Imura" <imura@af.airnet.ne.jp>

 * I meant no nead to include ${MASTERDIR}/../Makefile.inc.
 * 
 * Then what will be the category specific settings?

I don't know, but there might be some in the future.  For instance,
there was talk about adding EMACS_PORT support for emacs-related
ports.  Maybe we can put that in editors/Makefile.inc.

 * Do we have to move all CATEGORIES variables to Makefile.inc?

We don't have to, but that was one of the things I thought about too.
There can be a "CATEGORIES+=whatever" in all the Makefile.inc's.  That
way we can reduce most of the CATEGORIES lines (leaving only virtual
and extra secondary categories).  This could be even more beneficial
when we go to multi-level categories, since it will allow us to move
things around without having to change too much in the Makefiles
(basically the default category will mirror the directory structure).

 * I don't like it.

Why not?  Is there a case where a port in category X not having X in
the CATEGORIES line?

 * > We need to include both ${.CURDIR}/../Makefile.inc and
 * > ${MASTERDIR}/../Makefile.inc (in the order named) for the reason I
 * > mentioned above in 1).
 * 
 * Ok, you mean "after" or "before" is not the issue, right? :)

Um, I don't understand what you are trying to say, but the ordering
(${.CURDIR} before ${MASTERDIR}) is actually important so we can get
things like PKGNAMEPREFIX right.

Satoshi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?vqcn1n0i2pr.fsf>