[pkg-boost-devel] Fwd: Packaging of boost.compute

[Steve M. Robbins]

Hello,

On June 3, 2015 07:36:37 AM Ghislain Vaillant wrote:
> Dear Boost package maintainers,
> 
> I have a package (ArrayFire) which depends on boots.compute for its OpenCL
> backend. Although boost.compute has been accepted in the Boost family, it
> has benn yet to be released.
> 
> I heard rumours about it coming in 1.59 but you guys might be more aware of
> this than I am.

I don't know, myself.  Maybe Kyle can shed some light on this.

In terms of Boost in Debian; the current plan (Dimitri: please jump in if I 
mis-state things) is to wait until GCC 5 is the default compiler (because it 
will be C++11 mode by default), then package whatever is current.  Last I 
heard the GCC transition would be in July, so it may be that the Boost 
transition is later in the summer and we get Boost 1.59.  But there's also a 
good chance it would be 1.58.


> I just wanted to know whether you guys think it is worth to
> spending efforts to package boost.compute separately (similar to what is
> done with asio ?) or wait until the first official release with Boost comes
> out.
>
> According to the official Github repository, Boost.compute only requires
> Boost 1.48 or later + OpenCL + optional backend libraries like Eigen,
> VTK,...
> 
> Let me know what you guys think.

If you want to get ArrayFire in Debian before Compute is part of Debian's 
boost, you could package Compute separately as you suggest.  That means 
supporting it if other packages start using it and then deprecating it when 
Compute comes out in Debian's Boost.  Alternatively, and especially if yours 
is the only package needing it in the short term: you might consider not 
packaging it, but just including it in ArrayFire sources.

-Steve
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-boost-devel/attachments/20150607/0454c9bd/attachment.sig>