Package Details: vmlinux-to-elf 1.4.0-1

Git Clone URL: https://aur.archlinux.org/vmlinux-to-elf.git (read-only, click to copy)
Package Base: vmlinux-to-elf
Description: Recover a fully analyzable .ELF from a raw kernel, through extracting the kernel symbol table (kallsyms)
Upstream URL: https://github.com/marin-m/vmlinux-to-elf
Licenses: GPL-3.0-or-later
Conflicts: python-vmlinux-to-elf
Provides: python-vmlinux-to-elf
Submitter: vitaliikuzhdin
Maintainer: vitaliikuzhdin (marin-m)
Last Packager: marin-m
Votes: 1
Popularity: 0.007881
First Submitted: 2026-01-28 23:15 (UTC)
Last Updated: 2026-10-25 09:54 (UTC)

Latest Comments

vitaliikuzhdin commented on 2026-03-14 17:17 (UTC)

@marin-m, perhaps, but this is out of scope of the AUR packaging, it's not a good idea to use it here.

marin-m commented on 2026-03-14 14:48 (UTC)

Perhaps a vmlinux-to-elf-gui --install-metadata command can be bundled to install the XDG metadata autonomously after using uv or pip, when I think about it.

marin-m commented on 2026-03-14 09:52 (UTC) (edited on 2026-03-14 09:53 (UTC) by marin-m)

@vitaliikuzhdin In the Sideband package, installing Freedesktop metadata is actually done when running Setuptools with the --no-isolation (aka no-build-isolation-package) flag, this metadata is not part of the Wheel.

Cf. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=sideband&id=ad30850ac625848f312766827034727a93d4f2b9#n67

python -m build --wheel --no-isolation

Cf. https://github.com/markqvist/Sideband/blob/ead2427/setup.py#L107

    data_files = [
        ('share/applications', ['sbapp/assets/io.unsigned.sideband.desktop']),
        ('share/icons/hicolor/512x512/apps', ['sbapp/assets/io.unsigned.sideband.png']),
    ],

vitaliikuzhdin commented on 2026-03-14 07:56 (UTC)

@marin-m, I just remember packaging a project which installed icons and the desktop entry natively: https://aur.archlinux.org/packages/sideband

This also might be helpful if you'll decide to implement it: https://stackoverflow.com/a/2291791

marin-m commented on 2026-03-13 16:56 (UTC) (edited on 2026-03-13 16:57 (UTC) by marin-m)

I don't think that you can specify data to be auto-installed into {~/.,/usr/}local/share/{applications,metainfo,icons} from the metadata of a Wheel, that's outside of the scope of the format.

If your suggestion is to move the Desktop files at runtime when e.g first launching the GUI program, this sounds a bit hackish (this will leave untracked package files on the filesystem and will need a first run of the app from the command line) if I'm not mistaken

vitaliikuzhdin commented on 2026-03-13 12:25 (UTC)

@marin-m, this works but I thought you would add the files directly to the wheel so that non-AUR users will also have them without manual installs.

marin-m commented on 2026-03-12 20:39 (UTC)

Done in pkgrel 3, thanks for the suggestion

vitaliikuzhdin commented on 2026-03-12 17:36 (UTC)

@marin-m, updated and added the GUI dependencies as optional. It also might make sense to install an icon and a .desktop entry.

marin-m commented on 2026-03-12 16:21 (UTC)

@vitaliikuzhdin Hi, I pushed a 1.2.2 release with a pyproject.toml file that accepts Peewee ≥ 3.17, is it better this way?

If you update the PKGBUILD, it would be great to include the gui extra and install the PyGObject and GTK-4/libadwaita GIR dependencies as well, so that the new UI is available.

Regards

vitaliikuzhdin commented on 2026-03-04 14:14 (UTC)

Update to 1.0.2.post1 is blocked by python-peewee>=4.0.0.