grant@netbsd.org said:
> Modified Files: 
> [...]
> 	pkgsrc/lang/gcc3-c: Makefile
> [...]
> XXX why is GCC_PREFIX ${PREFIX}/gcc3 ?

Why not:-)
So it doesn't conflict "too much" with the monolithic gcc3
pkg, and one can use one to bootstrap the other.
(maybe this should be a variable...)
What used to conflict were the .info files which I could
live with. Now, after seb's changes, it is even better
and we can make them completely coexisting.

> please do not remove or cripple
> lang/gcc3. building all components would take considerably longer with
> these packages.

The compilation avoids duplication almost completely. Unpacking
and configure happen everytime, this cannot be avoided.
So I have to agree. We can use another name for a meta pkg.
(I'm not sure we need a meta pkg at all. Just a directory
for *.mk files to be pulled in. Shouldn't be called buildlink2.mk
btw but something like usecompiler.mk... It makes a difference
whether I need a compiler installed to build another language
module, or want to use it to build more or less unrelated stuff.)

best regards
Matthias