Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Feb 2009 11:49:43 +0800
From:      Li-Wen Hsu <lwhsu@FreeBSD.org>
To:        ports@freebsd.org
Subject:   Re: Status of devel/boost
Message-ID:  <1e39c0a90902191949h63543bd9w8ce8c4c0eaa5f7b8@mail.gmail.com>
In-Reply-To: <1e39c0a90902191947j612e3c3bo769cfb771a2f51a1@mail.gmail.com>
References:  <3cb459ed0902191459le2b20d5s14b13a032714802b@mail.gmail.com> <1e39c0a90902191947j612e3c3bo769cfb771a2f51a1@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Sorry that I forgot to cc ports@ list.

On Fri, Feb 20, 2009 at 11:47 AM, Li-Wen Hsu <lwhsu@freebsd.org> wrote:
> Hello,
>
> On Fri, Feb 20, 2009 at 6:59 AM, Alexander Churanov
> <alexanderchuranov@gmail.com> wrote:
>> Hi folks!
>>
>> Just want to synchronize our knowledge on this stuff.
>>
>> 1) The patch to update devel/boost from 1.34 to 1.37 is ready for several
>> months.
>
> That is great and I made another patch based on your own, which fixed
> some minor problems
> (includes building on amd64):
>
> http://people.freebsd.org/~lwhsu/boost-1.37.diff
>
>> 2) I've asked for taking a maintainership over devel/boost.
>>
>> 3) I am currently rebuilding all ports that depend on boost in order to
>> identify possible issues caused by update.
>
> Pav had an exp-run and here is the list of the ports which failed:
>
> http://people.freebsd.org/~lwhsu/boost-1.37.txt
>
> All OpenOffice.org ports are failed, openoffice.org-2.4.2_1.log is
> just one of them.
>
>> 4) There is a wiki page with more details:
>> http://wiki.freebsd.org/BoostPortingProject
>>
>> 5) Of course, to goal is to upgrade directly to 1.38 when all issues are
>> resolved.
>
> So are you working on a new patch currently?  Maybe you can based on
> my 1.37 patch
> (appply that first then update it to 1.38), this may help thing goes
> more smoothly.
>
>> 6) Another goal is to have all subsequent updates at corresponding dates of
>> boost releases.
>
> That's really a lot of work, maybe we also need to notify maintainers
> and see if upstream has
> newer version which supports newer version boost.  For the currently
> status, if we want have 1.37
> in the tree, the fastest way is repocopy devel/boost to devel/boost134
> and changes all the
> LIB_DEPENDS of the ports which needs 1.34 to build.  Maybe we just set
> a time to make
> this happen?
>
> Best Regards,
> Li-Wen Hsu
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1e39c0a90902191949h63543bd9w8ce8c4c0eaa5f7b8>