On Thu, 12 Jan 2006, Joerg Sonnenberger wrote:

> Fix build of boost on DragonFly.

I reported about boost problems on DragonFly to some boost developers back 
in August. I was told (in August) that some DragonFly fixes were committed 
then and that they would be available in version 1.33.1.

I see we are running 1.33.0. The 1.33.1 version I now see was released on 
December 5.

I don't know if that is related to your fixes or not (because I didn't 
check).

But it may be a good idea to make patches against the official versions.
 
This may help you because maybe some of the fixes may have already be 
done. And this may help other pkgsrc developers who update packages 
because they may have to recreate the patches. Coordinating with the 
MAINTAINERs may be a good idea just in case they are already in process of 
updating a package.

I do understand that some packages should not be updated just because a 
new version is available, but still asking MAINTAINER may be useful to 
discuss it.

Also, it would be good if all these code improvements were submitted 
upstream. That way other pkgsrc developers (or maintainers) do not have to 
recreate the patches again.

And also it may save your valuable time, because there have been cases 
where updates have lost patches -- probably because maintainer assumed 
that the patch was already upstream, or it didn't apply cleanly, or they 
just removed because didn't think was relevant anymore.

By the way, your code cleanup for many, many pkgsrc packages it greatly 
appreciated. I know it helps for many operating systems.

 Jeremy C. Reed

p.s. In August, I should have looked at this for pkgsrc's boost also, but 
I assumed it would get pulled into pkgsrc soon enough since I thought the 
boost would be released and updated. Then I forgot since I don't use 
boost on DragonFly (except for LyX).