Arch Linux

10025 readers

1 users here now

The beloved lightweight distro

founded 6 years ago

MODERATORS

k_o_t@lemmy.ml

PKGBUILD question (lemmy.blahaj.zone)

submitted 1 week ago by thesupertechie@lemmy.blahaj.zone to c/archlinux@lemmy.ml

10 comments fedilink hide all child comments

I'm trying to add a program that uses Python to the AUR. The app has no build script, and the main program uses files from other places in the repo directory. Should I just copy the repo files verbatim to the install directory and create a desktop file that runs the Python file?

If it helps, I'm trying to port the Mynah XMPP client.

you are viewing a single comment's thread
view the rest of the comments

[–] moonpiedumplings@programming.dev 4 points 1 week ago* (last edited 1 week ago) (1 children)

No, the correct solution is to use a python build system to package the application outlined according to the pyproject.toml in the git repo.

In addition to that, the de.nullhost.Mynah.yml is the recipe used to build the Flatpak.

Those to files are what you will have to adapt into the PKGBUILD, which is the recipe Arch linux uses to make packages.

[–] thingsiplay@lemmy.ml 2 points 1 week ago (2 children)

But it says the project doesn't have build files. How can it adapt and use a build system then?

[–] moonpiedumplings@programming.dev 1 points 1 week ago

the .yml file mentioned is a kind of build file, for flatpak.

[–] Strit@lemmy.linuxuserspace.show 0 points 1 week ago* (last edited 1 week ago) (1 children)

So it's just python scripts??

Maybe ask an AI to create a package for you to test. If it's working fine, edit the PKGBUILD to follow packaging guidelines and upload?

Also, it's made for flatpak. Why not just use that?

[–] thingsiplay@lemmy.ml 2 points 1 week ago

I don't know. Just wanted mention that the post says "The app has no build script", so it cannot follow your advice to use the build scripts. I actually have my own Python script that has no build script either on AUR too. It just downloads the script and puts in bin folder, plus the README and LICENSE files. And off course the dependencies to existing tools, as it is more or less a wrapper script.