Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.
--- Comment #57 from Hongli Lai <honglilai(a)gmail.com> 2010-04-16 18:40:30 EDT ---
Right now I'm working on a client project with a tight deadline.
Now, since this issue has been opened for about a year now I'll just be honest
with you. As part of a bootstrapping company I find it very hard to invest time
in getting my changes merged upstream. You mentioned that by submitting changes
upstream it'll alleviate myself of having to maintain the changes. This is
correct, but the flip side of the coin is that I'll have to get the changes
accepted in the first place. Some of the changes we made to Boost are quite
intrusive and change source and binary compatibility (we've modified some basic
classes to derive from classes in our own library, for example) and getting all
changes accepted into Boost will be a long, hard process. So what's easier,
maintaining the changes ourselves or going through the trouble of submitting
the changes upstream? I still think the former is easier.
Debian is already packaging Phusion Passenger and they know about our usage of
Boost. We already have contacts with people who are willing to maintain third
party yum repositories. Unlike the official Fedora repository, these third
party repositories can collaborate closely with us and won't lag behind
official releases for weeks or months.
So all in all I do not see any benefits in getting the Boost changes submitted
upstream; in fact, I only see drawbacks. If you want to do it I won't stop you,
but without some sort of financial compensation for my time I won't do it. I
have to work to pay for my food after all.
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.