[pkg-boost-devel] Packaging of standalone boost.compute

[Ghislain Vaillant]

On 25/07/15 03:22, Dimitri John Ledkov wrote:
> On 23 July 2015 at 19:49, Ghislain Vaillant <ghisvail at gmail.com> wrote:
>> Dear all,
>>
>> I queried the mailing list several times in the past month wrt the packaging
>> of Boost.Compute.
>>
>> The following options were suggested:
>>    * doing a multi-tarball release,
>>    * waiting for the release of Boost 1.59,
>>    * packaging Boost.Compute standalone.
>>
>> After further considerations, I'd be keen on going for the latter option. A
>> standalone Boost.Compute already exist from Kyle's PPA [1] and apart from
>> making sure both the standalone Boost.Compute and Boost 1.59 aren't
>> co-installable, I see little problems down the road. Besides, backporting to
>> earlier Debian and Ubuntu releases would be easier.
>>
>> As a reminder, I need Boost.Compute available as a b-dep for the OpenCL
>> backend of ArrayFire. It is currently the only missing dep, since both
>> clBLAS and clFFT have since been accepted in the archive.
>>
>> Please let me know of any objections / remarks / advice.
>>
>> Thanks for your work on Boost for Debian.
>
> I have looked into this. I have packaged boost 1.58 in the mean time.
>
> Boost.Compute is a header only library, and thus would be trial to integrate.
>
I guess you meant trivial?

> It should be part for 1.59 beta tarball, but wasn't due to unmerged
> pull requests into the master boost tarball generation project.
>
> I was going to integrate it by hand into 1.58. But didn't awaiting
> info from upstream about all of above.
>
> Would you be ok to have master snapshot of boost.compute in boost1.58
> package? if yes, please either help with a patch to add it in. (e.g.
> even a patch that adds all the headers will be fine) And then we can
> integrate it.
>
> Integrating it into boost1.58 now would be overall lower total cost of
> maintainance in debian (less uploads, less new queue, etc.)
>
> My currently highest priority is getting stuff ready for the
> gcc5/libstdc++6 transition. Cause that will be breaking all the world.
>
>

How about backporting? I personally intended to maintain a PPA for 
ArrayFire and deps (clBLAS, clFFT and potentially Boost.Compute) for 
Jessie / Ubuntu 14.04, which are the main distros used at my lab. Being 
forced to use Boost >= 1.58 or 1.59 would significantly complicate this 
goal.

Thoughts?

Ghis