Sunsetting this feedstock?

[jakirkham]

In PR ( conda-forge/staged-recipes#21953 ), cuda-cccl-impl is being added, which contains and supersedes cub.

Also this feedstock has been updated so that cub conflicts with cuda-cccl-impl (or other CCCL packages) ( #23 ). This conflict has also been applied as a repodata patch to old packages ( conda-forge/conda-forge-repodata-patches-feedstock#428 ).

Since the current plan is not to update this any further, how do we want to go about sunsetting this feedstock?

• Do we want to alias this package?
• Should this package emit some kind of deprecation warning?
• Would it make sense to run a migration to move to the preferred package?
• Do we want to archive this feedstock?
• Anything else we should do?
• Also any thoughts on the order/timeline of these?

Edit: Related thrust issue ( conda-forge/thrust-feedstock#19 )

[jakirkham]

cc @bdice @leofang @kkraus14

[jakirkham]

As the decision here will likely be the same as for thrust and discussion has already begun in the thrust issue ( conda-forge/thrust-feedstock#19 ), let's just discuss in that issue. Whatever resolution we come to, we can apply to both of these