On May 10, 2006, at 5:37 AM, joerg@britannica.bec.de wrote:

> On Wed, May 10, 2006 at 07:19:46AM +0000, Min Sik Kim wrote:
>>
>> Module Name:	pkgsrc
>> Committed By:	minskim
>> Date:		Wed May 10 07:19:46 UTC 2006
>>
>> Added Files:
>> 	pkgsrc/lang/sun-jre14: builtin.mk
>>
>> Log Message:
>> Add builtin.mk to use Darwin's native java.
>
> I've discussed this problem with schwarz@ on pkgsrcCon and I don't  
> like
> the builtin.mk usage here at all. In my opinion it just clutters the
> package, native JDK's should be handled separarely from java-vm.mk  
> only.

Could you elaborate this?  What makes jre packages different from  
other packages using builtin.mk?  I could move the builtin.mk logic  
into java-vm.mk, but what would it be better than having separate  
builtin.mk files?  At least the latter is consistent with the current  
pkgsrc convention in choosing a native implementation over a pkgsrc one.

Regards,
Min