From: ndowens <ndowens@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: evemu: New package
Date: Tue, 24 Nov 2020 20:46:25 +0100 [thread overview]
Message-ID: <20201124194625.z8wsRXtXoTREhCm4l9D5VRbjaOhSJGpEGjTIk4fEMJA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26623@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1129 bytes --]
New comment by ndowens on void-packages repository
https://github.com/void-linux/void-packages/pull/26623#issuecomment-733194908
Comment:
> ```diff
> diff --git a/srcpkgs/evemu/template b/srcpkgs/evemu/template
> index 12513aae59..2cbbaeb9c6 100644
> --- a/srcpkgs/evemu/template
> +++ b/srcpkgs/evemu/template
> @@ -3,7 +3,7 @@ pkgname=evemu
> version=2.7.0
> revision=1
> build_style=gnu-configure
> -hostmakedepends="automake pkg-config libtool python3"
> +hostmakedepends="pkg-config python3 asciidoc xmlto"
> makedepends="libevdev-devel"
> short_desc="Kernel device emulation"
> maintainer="Nathan Owens <ndowens@artixlinux.org>"
> @@ -11,7 +11,3 @@ license="LGPL-3.0-only"
> homepage="https://freedesktop.org/wiki/Evemu/"
> distfiles=${FREEDESKTOP_SITE}/evemu/evemu-$version.tar.xz
> checksum=78c9400d55eeeb5ab75161360543f9376438c4da4934cb34cdda5b46021ae379
> -
> -pre_configure() {
> - autoreconf -fi
> -}
> ```
>
> I don't know if splitting `-devel` is a good idea.
Splitting what? At first I thought meant I made a subpackage, e.g evemu-devel but only -devel I see is evdev-devel?
prev parent reply other threads:[~2020-11-24 19:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 1:51 [PR PATCH] " ndowens
2020-11-23 1:58 ` [PR PATCH] [Updated] " ndowens
2020-11-23 11:57 ` [PR REVIEW] " sgn
2020-11-23 15:16 ` [PR PATCH] [Updated] " ndowens
2020-11-23 15:26 ` ndowens
2020-11-24 14:22 ` sgn
2020-11-24 19:46 ` ndowens [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201124194625.z8wsRXtXoTREhCm4l9D5VRbjaOhSJGpEGjTIk4fEMJA@z \
--to=ndowens@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).