Skip to content

Migrate core plugins to C? #692

@ItsZariep

Description

@ItsZariep

As the title says, it might be a good idea to migrate core plugins to C. In recent months, most rolling release systems, like Arch Linux, have broken Xed plugins because:

Remove python3 loader
The loader is nonfunctional as of pygobject 3.52 because the latter was ported to libgirepository-2.0, which cannot be loaded together with libgirepository-1.0, which libpeas still depends on.

As a consequence, core Xed plugins written in Python don’t load because the plugin loader fails:

(xed:19216): libpeas-WARNING **: 12:31:31.714: Failed to load module 'python3loader': /usr/lib/libpeas-1.0/loaders/libpython3loader.so: cannot open shared object file: No such file or directory

(xed:19216): libpeas-WARNING **: 12:31:31.714: Could not load plugin loader 'python3'

** (xed:19216): WARNING **: 12:31:31.714: Failed to load builtin plugin: Text Size

** (xed:19216): WARNING **: 12:31:31.714: Failed to load builtin plugin: Join Lines

** (xed:19216): WARNING **: 12:31:31.714: Failed to load builtin plugin: Open URI

This has happened multiple times already, so I propose migrating these plugins to C, as some plugins, like Text Size, are fundamental features.

Plugins written in C don’t have this problem. I’m currently rewriting these plugins in C but I’m not sure if there are any considerations I should keep in mind during the process.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions