Arch Linux

jolife

Member

Registered: 2020-02-28

Posts: 5

Custom meta-package is not installing files.

I'm working on making a custom Arch installer script that includes the use of a meta-package downloaded via pacman from a LAN repo. Right now, the only file the package should be installing is a wheel file into /etc/sudoers.d
However, while everything else works like a charm, the sudoers file does not get installed. I tried running pacman in verbose mode, but got no indication of what might be failing. Note, there is no error. The package installs successfully, but when I check /etc/sudoers.d/ there is nothing there. Here is my PKGBUILD https://pastebin.com/DRxwY5Xq

I've spent hours on end trying to research this issue, but have found nothing to help.

Last edited by jolife (2020-03-11 15:49:48)

schard

Forum Moderator

From: Hannover

Registered: 2016-05-06

Posts: 2,610

Website

Re: Custom meta-package is not installing files.

&{pkgdir}

should be

${pkgdir}

That being said, you'll not get much help here, creating an usupported third-party installer.

---

Inofficial first vice president of the Rust Evangelism Strike Force

jolife

Member

Registered: 2020-02-28

Posts: 5

Re: Custom meta-package is not installing files.

&{pkgdir}

should be

${pkgdir}

That being said, you'll not get much help here, creating an usupported third-party installer.

Thanks, the samples for the PKGBUILD I found were wildly out of date. I figured out the other problems that arose from the PKGBUILD samples, but no documentation I found was indicating how to use the "install" command in package(). As to the "third party installer" bit, I felt this was a relevant post since it was related to package creation in general and not to an installer in and of itself. I appreciate the help!

eschwartz

Fellow

Registered: 2014-08-08

Posts: 4,097

Re: Custom meta-package is not installing files.

The "install" command is documented in "man install", and incorrectly failing to use correct bash programming syntax for variables is not the fault of any sort of documentation other than bash itself.

For future reference, if you ran "ls src/" from the same directory as the PKGBUILD, you would be able to debug what is going on here.

[eschwartz@arch /tmp/jolifes-pkgbuild] $ ls src/
&{pkgdir}/  sudoers.wheel@
[eschwartz@arch /tmp/jolifes-pkgbuild] $ tree src pkg
src
├── &{pkgdir}
│   └── etc
│       └── sudoers.d
│           └── wheel
└── sudoers.wheel -> /tmp/jolifes-pkgbuild/sudoers.wheel
pkg
└── lts-arch-base

Last edited by eschwartz (2020-03-11 19:52:02)

---

Managing AUR repos The Right Way -- aurpublish (now a standalone tool)