| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
Use it for librechroot, libremakepkg, libremkchroot
|
|
I did this by making the assumption that the files in a directory are
dividable into 2 groups: those that are executable, and those that aren't, and
that all of the files in each group all go in the same folder when
installed.
These install directories are configurable per source directory with
$(libre_execdir) and $(libre_datadir)
|
|
chcleanup:
* load `CHROOTEXTRAPKGS` from `/etc/libretools.d/chroot.conf`
* always cleanup temporary files
* properly quote the various arrays used
* verify that you are in a chroot
librechroot:
* write `$copydir/etc/libretools.d/chroot.conf`
libremakepkg.gpl2:
* use `librechroot` instead of `archroot` directly in `chrootexec()`
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://labs.parabola.nu/issues/154
|
|
https://labs.parabola.nu/issues/252
|
|
|
|
|
|
Conflicts:
src/aur
src/chroot-tools/librechroot
src/librerepkg
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
base-devel
|
|
|
|
mkarchroot/archroot's option parsing is a little less flexible (but a lot
more understandable) than it was before.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This includes the notorious command-not-found error triggered in
libremakepkg
|
|
|
|
|
|
|
|
|
|
|
|
|
