From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] fastd: Update to 17
Date: Wed, 23 Mar 2016 11:41:01 +0000 [thread overview]
Message-ID: <1458733261.30749.78.camel@ipfire.org> (raw)
In-Reply-To: <1458723703-790-1-git-send-email-alexander.marx@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1359 bytes --]
Hi,
a quick update on dependencies:
You added libuecc >= 5 which works, because libuecc-devel cannot be installed in
an older version when libuecc >= 5 is installed. However we usually write
"libuecc-devel >= 5". Just because it is shorter...
Will you send an updated patch?
Best,
-Michael
On Wed, 2016-03-23 at 10:01 +0100, Alexander Marx wrote:
> Signed-off-by: Alexander Marx <alexander.marx(a)ipfire.org>
> ---
> fastd/fastd.nm | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/fastd/fastd.nm b/fastd/fastd.nm
> index 23563cf..80bd695 100644
> --- a/fastd/fastd.nm
> +++ b/fastd/fastd.nm
> @@ -4,7 +4,7 @@
> #############################################################################
> ##
>
> name = fastd
> -version = 16
> +version = 17
> release = 1
>
> groups = Networking/VPN
> @@ -17,16 +17,18 @@ description
> to run on embedded devices.
> end
>
> -source_dl =
> +source_dl = https://projects.universe-factory.net/attachments/download/81/
> sources = %{thisapp}.tar.xz
>
> build
> requires
> bison >= 2.5
> cmake >= 3.0
> + doxygen
> json-c-devel
> libcap-devel
> libsodium-devel
> + libuecc >= 5
> libuecc-devel
> openssl-devel
> end
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-23 11:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 9:01 Alexander Marx
2016-03-23 11:41 ` Michael Tremer [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=1458733261.30749.78.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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