feat(makechrootpkg): Add "-i" to install packages from repository.
Technically it should be within the PKGBUILD file, but just having this parameter makes scripting and automating makechrootpkg much easier in the cases it doesn't. Otherwise one would have to handle patching the PKGBUILD which may fail once the file gets updated, where as just manually installing a package is almost always successful and therefore much better for scripted/automated usage. Also just having this option simplifies debugging side effects and dependency errors using clean builds that have specific additional packages installed.
E.g. makechrootpkg -c -u -T -U builduser -n -C -r /aur_chroot -i suspectedpackage
Merge request reports
Activity
- Resolved by Klaus Frank
I don't think this is a use case we want to support
Whats the point of building a package in a chroot if it misses dependencies anyways?
- Resolved by Klaus Frank
Regarding the development workflow improvements we will release the possibility to automatically change into the chroot (see !177 (merged)) with the next release %v1.1.0.
added resolutionwont-fix label
mentioned in merge request !214 (closed)
Regardless of the "instead of working around missing dependencies, fix it in the original AUR repo" (I concede here and declare defeat), how exactly is the current supposed way to deal with optional build dependencies? Without an "-i" or similar?
Or when the referenced package is ambiguous and provided by multiple packages. How do you select the desired/correct ones? Just create independent AUR repositories to build the same package in different flavors and hardcode individual packages instead of a meta package/group?
added 5 commits
-
6a8a842d...c2d73d73 - 4 commits from branch
archlinux:master
- fcbcd128 - feat(makechrootpkg): Add "-i" to install packages from repository.
-
6a8a842d...c2d73d73 - 4 commits from branch