Date: Fri, 3 Apr 2009 02:44:13 +0400 From: Dmitry Marakasov <amdmi3@amdmi3.ru> To: Alexander Churanov <alexanderchuranov@gmail.com> Cc: ports@freebsd.org, Jeremy Messenger <mezz7@cox.net>, lwhsu@freebsd.org Subject: Re: Status of devel/boost upgrade Message-ID: <20090402224413.GV1964@hades.panopticon> In-Reply-To: <3cb459ed0904020821u3051c572l6461274ae7ff118b@mail.gmail.com> References: <3cb459ed0903270809s2da0fce7i66686a176d369931@mail.gmail.com> <20090331230246.GN1964@hades.panopticon> <op.urotvvn79aq2h7@localhost> <20090401113857.GO1964@hades.panopticon> <3cb459ed0904020821u3051c572l6461274ae7ff118b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
* Alexander Churanov (alexanderchuranov@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 amdmi3@amdmi3.ru ..: jabber: amdmi3@jabber.ru http://www.amdmi3.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090402224413.GV1964>