Differences between buildpkg and chrootbuild

[callegar]

Hi, I have noticed that two tools exist to build packages in a chroot: buildpkg and chrootbuild.

However the reason why there are two tools and the differences between them are not clear to me.

• Which one should one generally use?
• Are there things that one tool can do and the other cannot?

Thanks

[callegar]

Might have found the answer myself (and from a 2022 thread started by myself!): got the answer that buildpkg is not anymore maintained and that chrootbuild should be used instead. Can this info be added to the readme in the git project to which buildpkg belongs?

[scotty65]

@callegar

Might have found the answer myself (and from a 2022 thread started by myself!): got the answer that buildpkg is not anymore maintained and that chrootbuild should be used instead.

Yes - a quick forum search for buildpkg does bring up a few results with the above advice. For example:

Not able to build pdfsam AUR package for a custom Manjaro ISO

archlinux-java-run is an AUR package, so it must be installed manually in the chroot. FYI, buildpkg from manjaro-tools-pkg-git is deprecated in favor of chrootbuild from manjaro-chrootbuild. sudo chrootbuild -c -p pdfsam -i /path/to/archlinux-java-run-11-1-any.pkg.tar.zst

@callegar

Can this info be added to the readme in the git project to which buildpkg belongs?

I was just thinking along similar lines. Maybe also a message that buildpkg is deprecated in favor of chrootbuild when the buildpkg command is run (if a deprecated message isn’t already there)?