Package Details: eventd-git 0.27.0.r0.g5efcfe1a-1

Git Clone URL: https://aur.archlinux.org/eventd-git.git (read-only, click to copy)
Package Base: eventd-git
Description: A small daemon to act on remote or local events
Upstream URL: https://www.eventd.org
Licenses: GPL3, MIT, LGPL3
Conflicts: eventd
Provides: eventd
Submitter: sardemff7
Maintainer: sardemff7
Last Packager: sardemff7
Votes: 0
Popularity: 0.000000
First Submitted: 2016-05-28 09:54 (UTC)
Last Updated: 2019-10-19 12:34 (UTC)

Latest Comments

1 2 Next › Last »

sardemff7 commented on 2018-03-08 13:35 (UTC)

You can join on IRC and drop a comment, I’m quite reactive and it may take a few minutes until I fix your issue :-) Also, I’m actually quite picky with PRs, code style and changes, so it might save you some time. ;-)

Omar007 commented on 2018-03-08 13:02 (UTC)

Great :)

Really enjoying the software so far. Have one gripe with it atm, might look into making a PR for that at some point once I've looked into it ;)

sardemff7 commented on 2018-03-07 17:59 (UTC)

I was planing a release soon, and here it is. And yet, I failed at using the right commit in the version, so here it is, with a pkgrel bump. ;-)

Omar007 commented on 2018-03-07 13:16 (UTC)

You should really be bumping it now.. Anyway, if you ever decide to make quality/up-to-standard packages, you know where to look now. I'll leave you with that.

Thanks for at least making it so it can actually build though :)

sardemff7 commented on 2018-03-07 12:41 (UTC)

Yeah I understand the pkgrel concept, but I find it weird on a package that is always rebuilt. Anyway, I’ll do that on future changes.

However, I will never hide a direct dependency of a package, it is not correct. :-)

Omar007 commented on 2018-03-07 12:15 (UTC) (edited on 2018-03-07 12:18 (UTC) by Omar007)

It certainly is relevant. You should probably read up on how to package for Arch.

For packages in general: https://wiki.archlinux.org/index.php/arch_packaging_standards#Package_etiquette

Additional info for versioned packages: https://wiki.archlinux.org/index.php/VCS_package_guidelines#Guidelines

In short/relation to the dependencies and pkgrel:

1) pkgrel should always be increased if the pkgver does not change. If the pkgver is increased, the pkgrel resets back to 1. In case of versioned packages, if there are no new commits to the software, you have to increase the pkgrel if you make changes to the PKGBUILD as the pkgver doesn't change. If there are new commits to a git package since the last PKGBUILD commit, you should commit with the new pkgver instead (and (re)set pkgrel to 1).

2) Dependencies should not be included if already satisfied due to another dependency

You can catch a ton of issues (these and more) with your package by using namcap to analyze the package. You can catch even more by also building in a clean chroot (e.g. if it builds in a clean chroot, you know all your makedepends are covered).

sardemff7 commented on 2018-03-07 09:47 (UTC)

It’s a -git package, pkgrel isn’t exactly relevant, is it? Or either I’d have to reset it every time I do a commit (which is unpractical even when you’re upstream) or never and it’ll grow unbounded.

And I don’t like hidden dependencies, libxkbcommon is required directly, not just as a libxkbcommon-x11 dep. I should add xkeyboard-config too, actually.

Omar007 commented on 2018-03-06 23:20 (UTC)

That was quick :O

A few quick pointers though; you forgot to bump the pkgrel and the libxkbcommon dependency is already satisfied/included by libxkbcommon-x11. You don't need to add that explicitly.

sardemff7 commented on 2018-03-06 22:02 (UTC)

Thanks for the report, fixed now. :-)

Omar007 commented on 2018-03-06 21:52 (UTC)

Requires git and libxkbcommon-x11 as a makedepends. Will not build without.

1 2 Next › Last »