tool.blender.ensure_bin_in_path issue in packaged context

[CyrilWaechter]

Bug Description

Another packaged context issue. When activating Bonsaï using AUR package I get message below. I might be wrong but there is a bin folder only if these binaries are not already available system-wide.

Attachments

No response

Debug and Error Output

Exception in module register(): /usr/share/blender/4.5/extensions/system/bonsai/__init__.py
Traceback (most recent call last):
  File "/usr/share/blender/4.5/scripts/modules/addon_utils.py", line 515, in enable
    mod.register()
    ~~~~~~~~~~~~^^
  File "/usr/share/blender/4.5/extensions/system/bonsai/__init__.py", line 278, in register
    bonsai.bim.register()
    ~~~~~~~~~~~~~~~~~~~^^
  File "/usr/lib/python3.13/site-packages/bonsai/bim/__init__.py", line 280, in register
    tool.Blender.ensure_bin_in_path()
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/lib/python3.13/site-packages/bonsai/tool/blender.py", line 486, in ensure_bin_in_path
    for filename in os.listdir(bin_dir):
                    ~~~~~~~~~~^^^^^^^^^
FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/python3.13/site-packages/bonsai/libs/bin'

[Moult]

See 34a2d95 ping @brunopostle

[brunopostle]

Odd, there is a bonsai/libs/bin folder in the repo, but it doesn't have any files in it, so I guess it isn't being created in this AUR package. Solution might be to drop a README file into it.

[CyrilWaechter]

Odd, there is a bonsai/libs/bin folder in the repo, but it doesn't have any files in it, so I guess it isn't being created in this AUR package. Solution might be to drop a README file into it.

You are right. I don't understand where in packaging process the folder is lost. I'll look into it.

[brunopostle]

Assuming that this AUR Bonsai is a distro packaged version of Bonsai.

This bin folder exists to contain any command-line tools that Bonsai needs, the folder is added to the PATH on startup so we don't have to mess around with installing executables to different places on different platforms.

Currently the Bonsai Makefile downloads the latest ifcmerge, puts it in here and makes it executable. Any Linux distro package should do the same.

Note that this mechanism can be used to easily add any executables that Bonsai needs in the future.