OK, guys,
As I see everybody agrees on splitting boost into several ports and on
Boost.Python beeing a separate port. Let's proceed with option #2
("jam", "libs", "python-libs" and "docs").
Personally, I like the idea #4 of having source-libs and a port per a
shared library. I'd like to have another discussion on that when some
statistics on boost usage in ports is ready.
I have questions on how to perform this task:
1) Given that port freeze starts on 13th, are there any chances to
have boost-1.38 splitted into several packages in 7.2-RELEASE?
2) Is is permitted to test patch for updating to 1.38 with some ports,
not with all that depend on boost and then file a PR, specifying which
ports were tested? The aim is to omit building and testing some ports
(like openoffice) myself.
Sincerely,
Alexander Churanov,
maintainer of devel/boost
_______________________________________________
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"
