Building source: "clean chroot?" "script or manually?"

Gnew Stemdee · 2017-11-06 07:22:17

As an exercise, I went through the process of building a core repo package, ed the editor, from source. Used asp and svn to fetch PKGBUILD and files needed per wiki https://wiki.archlinux.org/index.php/Arch_Build_System. Used a clean chroot "Convenience Way" https://wiki.archlinux.org/index.php/De … ean_Chroot, installed devtools and used the extra-x86_64-build script.

The extra-x86_64-build script curiously promped for my sudo password right away. After dealing with the pgp key, the build proceeded normally.
I also noticed the script actually installed ed in the chroot /var/lib/archbuild/extra-x86_64/uzer/bin/ after building the package.

I understand for system safety, AUR packages built with makepkg as user and not root. I also understand the repo packages are on an entirely different level of trust compared to AUR.

So some reading after: chroot requires root privilege https://wiki.archlinux.org/index.php/ch … quirements
Also a section for alternatives without root privileges. https://wiki.archlinux.org/index.php/ch … privileges

A few questions. Why the script installs ed in chroot?

Do you all use clean chroot (with script or manually) on your everyday or dedicated build systems.

Does it depend if package used on build system or other systems?

Thanks

WorMzy · 2017-11-06 09:28:55

Why the script installs ed in chroot?

Presumably so that devs can test that the package installs correctly and the install scriptlet (if any) runs successfully before they push it out to a repository.

Do you all use clean chroot (with script or manually) on your everyday or dedicated build systems.

Yes. All my foreign packages are built with a clean chroot. Some end up in my personal repository which is used to distribute my built packages to all of my machines (laptop, work, home desktop)

Does it depend if package used on build system or other systems?

If you start with a well written PKGBUILD and build it in a clean chroot, then the resulting package should install and work properly on any Arch install*. If you use makepkg directly, then you end up with a package which, depending on the build system, may have undeclared dependencies. A lot of build systems are greedy -- if they can build with feature X when package X is available, they will, even if the PKGBUILD writer did not write the PKGBUILD with this in mind.

* assuming you built the package for the architecture of the destination PC. i.e. You can't install a x86_64 package on an i686 arch install and expect it to work just because it was built in a clean chroot.

Slithery · 2017-11-06 10:29:06

Gnew Stemdee wrote:

Do you all use clean chroot (with script or manually) on your everyday or dedicated build systems.

Yep. I use clean-chroot-manager on my build machine and push the packages to a custom repo.

Trilby · 2017-11-06 11:32:27

Gnew Stemdee wrote:

Do you all use clean chroot (with script or manually) on your everyday... systems.

No. I never have.

Very much like I don't read the front page arch linux news before updating my system. At the first sign of trouble without an obvious solution, though, I do read the news. Just the same, any trouble building a package with just `makepkg -si` I first assume may be due to peculiarities of my system and if I don't find evidence to the contrary I'd try a clean chroot before assuming there was a problem in the package.

But note that I quoted what I was responding to: this is for my everyday system(s) for personal use, not a build server to distribute built packages. I'd say anyone doing the latter must use a clean chroot.

Last edited by Trilby (2017-11-06 11:32:50)

graysky · 2017-11-06 12:40:04

For packages of high familiarty, I just build with makepkg. Most others I use a clean chroot for a personal repo shared on my lan and amoung friends...That’s most of why I wrote clean-chroot-manager linked by slithery above.

cfr · 2017-11-10 01:02:24

Gnew Stemdee wrote:

Do you all use clean chroot (with script or manually) on your everyday or dedicated build systems.

Never. But I would do this if I was going to share the built package or if I was testing a PKGBUILD which I planned to share.

I build almost all packages as a dedicated user, however i.e. not as my usual user. I only build as me if the package won't build otherwise, I understand why it won't build otherwise and I'm more-than-usually confident about the PKGBUILD. This applies to very few packages, though. Almost everything builds fine as my other user.

Arch Linux

#1 2017-11-06 07:22:17

Building source: "clean chroot?" "script or manually?"

#2 2017-11-06 09:28:55

Re: Building source: "clean chroot?" "script or manually?"

#3 2017-11-06 10:29:06

Re: Building source: "clean chroot?" "script or manually?"

#4 2017-11-06 11:32:27

Re: Building source: "clean chroot?" "script or manually?"

#5 2017-11-06 12:40:04

Re: Building source: "clean chroot?" "script or manually?"

#6 2017-11-10 01:02:24

Re: Building source: "clean chroot?" "script or manually?"

Board footer