public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. ca762aaf6e9e0062168b145b935171713c88d2b5
Date: Sat, 12 Dec 2015 17:54:06 +0100	[thread overview]
Message-ID: <20151212165406.7BA8721445@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2835 bytes --]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".

The branch, next has been updated
       via  ca762aaf6e9e0062168b145b935171713c88d2b5 (commit)
      from  0909a0a1d8873ac694a3eab0c91e10e0f5cd486f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit ca762aaf6e9e0062168b145b935171713c88d2b5
Author: Matthias Fischer <matthias.fischer(a)ipfire.org>
Date:   Sat Dec 12 14:10:16 2015 +0100

    arping: Update to 2.15
    
    arping: Update to 2.15
    
    Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
    Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
    Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>

-----------------------------------------------------------------------

Summary of changes:
 lfs/arping | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

Difference in files:
diff --git a/lfs/arping b/lfs/arping
index 13eb05e..86f7279 100644
--- a/lfs/arping
+++ b/lfs/arping
@@ -1,7 +1,7 @@
 ###############################################################################
 #                                                                             #
 # IPFire.org - A linux based firewall                                         #
-# Copyright (C) 2007  Michael Tremer & Christian Schmidt                      #
+# Copyright (C) 2015  Michael Tremer & Christian Schmidt                      #
 #                                                                             #
 # This program is free software: you can redistribute it and/or modify        #
 # it under the terms of the GNU General Public License as published by        #
@@ -24,7 +24,7 @@
 
 include Config
 
-VER        = 2.05
+VER        = 2.15
 
 THISAPP    = arping-$(VER)
 DL_FILE    = $(THISAPP).tar.gz
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
 
 $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
 
-$(DL_FILE)_MD5 = 96e7c2ce8ae09046e264a314eeaac4dd
+$(DL_FILE)_MD5 = 676584f6eb4ccc8c70fc6b2c702df75d
 
 install : $(TARGET)
 
@@ -70,7 +70,11 @@ $(subst %,%_MD5,$(objects)) :
 $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
 	@$(PREBUILD)
 	@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
+	cd $(DIR_APP) && ./bootstrap.sh
+	cd $(DIR_APP) && ./configure --prefix=/usr
+
 	cd $(DIR_APP) && make $(MAKETUNING)
-	cd $(DIR_APP) && install -m 0755 arping /usr/sbin
+	cd $(DIR_APP) && make install
+
 	@rm -rf $(DIR_APP)
 	@$(POSTBUILD)


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2015-12-12 16:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20151212165406.7BA8721445@argus.ipfire.org \
    --to=git@ipfire.org \
    --cc=ipfire-scm@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