split xcbgen from xcb-proto

[Ashish SHUKLA]

Andriy Gapon writes:
> on 08/05/2009 10:06 Ashish SHUKLA said the following:
>> Andriy Gapon writes:
>> 
>>> It seems that it is a kind of bloating to require python with X (even if only a
>>> small portion of it is needed). Unfortunately upstream guys maintain xcb-proto and
>>> xcbgen in the same distribution. But a trend among packgers seem to be to split
>>> these two into separate packages. I wonder if anybody is working on the same for
>>> our ports.
>> 
>> I don't think splitting into two ports will be a good idea.

> Why?
> They did it this way in pkgsrc and in debian packages. It seems natural
> to have C stuff as one port/package and python libs for transforming XML
> as another.

Well no ideas about netbsd's pkgsrc system, but debian is a package
based system. Being a package based system, you've to create a separate
package for each combination of options you're going to support. IMHO,
FreeBSD is not a package based system primarily. It is ports based and
in ports based system you've the freedom to specify the OPTIONS with
which you want port to be installed and a package to be built for it.

And BtW, WITH_PYTHON is not defined by default which means the default
port will not be built with python support, unless you specifically
requests for it. If this seems okay to you, I can add OPTIONS.

> -- 
> Andriy Gapon

-- 
Ashish SHUKLA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20090508/d0e5bc52/attachment.pgp