* Alexander Churanov (alexanderchura...@gmail.com) wrote: > I've already did it about a month ago. Currently I'm testing the > solution. There are two ideas about splitting boost:
Woo, this is great! > 1) Split it into bjam, source-libs, shared-libs, python-libs and docs. > This is what was actually done by me. > 2) Split it into bjam, docs and a separate port for each library. This > needs discussion. Not sure if splitting it into many small libraries is a good idea. How many are there, btw? Is it a port per libboost_*so, or per include/boost/* ? Also splitting shared libs and source libs is a strange idea - there will be confusion on which port does specific library belong and it seems very likely that most boost-using ports will depend on both ports. Boost-python is a must to be split into separate port because it has an extra dependency, docs too, because not many people need them, bjam, well, because it's a build tool, and everything else may be left in a single port. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ru http://www.amdmi3.ru _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
