Arch Linux User Repository

@ioquatix:

Sure, I haven't been building my New Relic PKGBUILDs from source out of convenience and speed. I'll see if I can set up a PKGBUILD to build from source, and then propose an MR/PR.

As you can see, I've submitted three NRI plugins to the AUR. I'm sure there are more that others use; these are only the ones I use currently.

It will be a couple of weeks before I'm able to draft the New Relic article on the Wiki. The first step was submitting all my PKGBUILDs to the AUR, now I can draft a stub on the Wiki. I'll post again here once I've done so.

@ectospasm I'm happy to add you as a maintainer if you have a vision for how to move things forward.

I've found the recommended way to set up New Relic on a host (namely, running the New Relic CLI command so it does all the work for you) doesn't work in Arch, since it's not officially supported by New Relic.

Over the past several months I've been working on my own PKGBUILDs to get New Relic installed on my Arch VPS; I'm putting them all into the newrelic group. I'm now at a point where I'm comfortable publishing my PKGBUILDs to the AUR. My PKGBUILDs use the binary packages released on the various New Relic GitHub pages, at least wherever possible.

But that means at least one of my PGKBUILDs (i.e., newrelic-infra-bin, not published to the AUR at the moment) conflicts with this package. I think that's OK; the two can coexist in the AUR, and I set newrelic-infra-bin provides and conflicts with newrelic-infra in my PKGBUILD (so the two can't coexist if they're installed via makepkg/pacman on the same system). I don't think this older AUR package needs to be updated or removed (other than a version bump); I'm just announcing it here as a courtesy.

My plans after this are to create two pages on the Arch Wiki: one for Observability, and one specifically for New Relic on Arch. I don't see any mention of New Relic on the Arch Wiki currently, so I'm not sure how one would use the AUR package newrelic-infra by itself to get a fully functional New Relic system working on Arch.

EDIT: I believe any AUR package that is simply a repackaging of a binary file (either a package from another distro, or built by the upstream project) should have the -bin package name suffix. If an AUR package doesn't have this suffix, I expect it to be built from source if it's supposed to be a compiled binary installed at the end of it. So I've posted newrelic-infra-bin from New Relic's own .tar.gz file, instead of from an .rpm or .deb (the latter is what the newrelic-infra AUR package does). You're welcome to keep this as a binary package, but I recommend refactoring this PKGBUILD so it builds from source (since the New Relic Apache 2.0 license allows it).

@roobre I've added you as a co-maintainer.

Hey @ioquatix

I'm pasting a patch to bump to the latest release at the time of witing (1.15.2).

If you'd like some helm maintaining this, I currently work at New Relic and I'd be happy to step-up and lend you a hand with it. Just to clarify, I'd be doing this on my free time and it is not in New Relic plans to officially support this package. However I'll do my best to keep it updated and working as long as I have some spare time for it :)

Please tell me what you think.

Patch follows:

diff --git a/PKGBUILD b/PKGBUILD
index 8ad67e4..b1d2459 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -1,17 +1,17 @@

 pkgname=newrelic-infra
-pkgver=1.11.26
+pkgver=1.15.2
 pkgrel=1
 license=('custom')
 arch=('x86_64')
 depends=('curl')
 url=https://download.newrelic.com/infrastructure_agent/linux/apt/pool/main/n/newrelic-infra
 source=($url/newrelic-infra_systemd_${pkgver}_systemd_amd64.deb)
-sha256sums=('6123dcc1c206db060675feecc978662441347c6ad697bf2b56d5cf2f244ca321')
+sha256sums=('5051958c7df07c4425649440694b5ebece7a33b48f01b8c238f3b4708cbf8f00')

 package() {
        tar xvf "${srcdir}/data.tar.gz"
-
+       rm -r "${srcdir}/var/run"
        cp -Ra "${srcdir}/etc" "${pkgdir}"
        cp -Ra "${srcdir}/usr" "${pkgdir}"
        cp -Ra "${srcdir}/var" "${pkgdir}"

I've updated this to 1.11.26. However, I'm no longer using this package, so if you want to become a co-maintainer, please let me know.