# vtkbool as remote module

**URL:** https://discourse.vtk.org/t/vtkbool-as-remote-module/15182
**Category:** Development
**Created:** [January 20, 2025, 10:04am UTC](https://discourse.vtk.org/t/vtkbool-as-remote-module/15182 "2025-01-20T10:04:51Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![kenavolic](https://discourse.vtk.org/user_avatar/discourse.vtk.org/kenavolic/32/7886_2.png) [@kenavolic](https://discourse.vtk.org/u/kenavolic)
#### Post date: [January 20, 2025, 10:04am UTC](https://discourse.vtk.org/t/vtkbool-as-remote-module/15182/1 "2025-01-20T10:04:51Z")

</div>

Hi everybody,

I read about the standard for a module to be included as a remote module ([VTK/Remote Modules - KitwarePublic](https://vtk.org/Wiki/VTK/Remote_Modules)).

For those who know the vtkbool project ([GitHub - zippy84/vtkbool: A new boolean operations filter for VTK](https://github.com/zippy84/vtkbool)), what would you say would be the minimal work to do in order for it to be eligible as a remote module (let’s say like vtk-dicom)?

Thanks for your help,  
Best Regards

---

<div class="post-metadata">

### Author: ![danlipsa](https://discourse.vtk.org/user_avatar/discourse.vtk.org/danlipsa/32/390_2.png) [@danlipsa](https://discourse.vtk.org/u/danlipsa)
#### Post date: [January 20, 2025, 2:56pm UTC](https://discourse.vtk.org/t/vtkbool-as-remote-module/15182/2 "2025-01-20T14:56:38Z")

</div>

Please see the following discussion and MR:

> [@Adding Roemer's Boolean Filter as a Remote Module](https://discourse.vtk.org/t/adding-roemers-boolean-filter-as-a-remote-module/1635/37):
>
> Hello. Are there any news about the python wrapper for remote modules? Ronald

---

<div class="post-metadata">

### Author: ![Ron84](https://discourse.vtk.org/user_avatar/discourse.vtk.org/ron84/32/630_2.png) [@Ron84](https://discourse.vtk.org/u/Ron84)
#### Post date: [January 22, 2025, 5:38pm UTC](https://discourse.vtk.org/t/vtkbool-as-remote-module/15182/3 "2025-01-22T17:38:26Z")

</div>

That thread is about 5 years old. 🤣

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.vtk.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.vtk.org/u/ben.boeckel)
#### Post date: [February 23, 2025, 3:21am UTC](https://discourse.vtk.org/t/vtkbool-as-remote-module/15182/4 "2025-02-23T03:21:38Z")

</div>

> [@kenavolic](#):
>
> what would you say would be the minimal work to do in order for it to be eligible as a remote module (let’s say like vtk-dicom)?

Existing remote modules are essentially “grandfathered in” from their inclusion as such in older VTK versions (pre-9.0). For various reasons, pre-9.0 VTK did not provide a suitable environment for wrapping VTK code from VTK’s install tree. This has been resolved since then.

So, the bar is pretty high for this. What benefits are available by making it a remote module. Note the downsides:

- lack of control on the code when making changes (VTK tracks it by hash, so any changes VTK makes that require updates means making PRs elsewhere)
- for the above reason, CI does _not_ use remote modules
- ends up requiring the network for packaging from source tarballs (as remote modules are not _in_ the source tarball)