All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] zeroconf: remove
Date: Wed, 22 Aug 2012 16:50:27 +0100	[thread overview]
Message-ID: <1345650627-3232-1-git-send-email-paul.eggleton@linux.intel.com> (raw)

We already have avahi in OE-Core and some cursory research suggests that
avahi is preferred over this package, which has apparently not seen a
release since 2006. Nothing in OE-Core actually refers to it, so let's just
remove it.

CC: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
 .../zeroconf/zeroconf/compilefix.patch             |   19 --------
 .../zeroconf/zeroconf/debian-zeroconf              |   51 --------------------
 .../zeroconf/zeroconf/zeroconf-default             |   17 -------
 meta/recipes-connectivity/zeroconf/zeroconf_0.9.bb |   34 -------------
 4 files changed, 121 deletions(-)
 delete mode 100644 meta/recipes-connectivity/zeroconf/zeroconf/compilefix.patch
 delete mode 100644 meta/recipes-connectivity/zeroconf/zeroconf/debian-zeroconf
 delete mode 100644 meta/recipes-connectivity/zeroconf/zeroconf/zeroconf-default
 delete mode 100644 meta/recipes-connectivity/zeroconf/zeroconf_0.9.bb

diff --git a/meta/recipes-connectivity/zeroconf/zeroconf/compilefix.patch b/meta/recipes-connectivity/zeroconf/zeroconf/compilefix.patch
deleted file mode 100644
index 328e574..0000000
--- a/meta/recipes-connectivity/zeroconf/zeroconf/compilefix.patch
+++ /dev/null
@@ -1,19 +0,0 @@
-| zeroconf.c: In function 'main':
-| zeroconf.c:145: error: 'PATH_MAX' undeclared (first use in this function)
-
-RP - 4/9/09
-
-Upstream-Status: Pending
-
-Index: zeroconf-0.9/zeroconf.c
-===================================================================
---- zeroconf-0.9.orig/zeroconf.c	2009-09-04 10:05:25.000000000 +0100
-+++ zeroconf-0.9/zeroconf.c	2009-09-04 10:05:42.000000000 +0100
-@@ -33,6 +33,7 @@
- #include <net/if_arp.h>
- #include <sys/time.h>
- #include <signal.h>
-+#include <limits.h>
- 
- #include "delay.h"
- 
diff --git a/meta/recipes-connectivity/zeroconf/zeroconf/debian-zeroconf b/meta/recipes-connectivity/zeroconf/zeroconf/debian-zeroconf
deleted file mode 100644
index c3705d2..0000000
--- a/meta/recipes-connectivity/zeroconf/zeroconf/debian-zeroconf
+++ /dev/null
@@ -1,51 +0,0 @@
-#!/bin/sh
-
-if [ ! -x /usr/sbin/zeroconf ]; then
-    exit 0
-fi
-
-# IPv4 link-local addresses (zeroconf) are
-# only applicable on the 'inet' address family
-[ "X$ADDRFAM" != "Xinet" ] && exit 0
-
-# However there are some methods where it doesn't
-# make any sense to configure an IPv4LL address
-
-# not on loopback
-[ "X$METHOD" = "Xloopback" ] && exit 0
-
-# not on ppp or wvdial either
-[ "X$METHOD" = "Xppp" ] && exit 0
-[ "X$METHOD" = "Xwvdial" ] && exit 0
-
-# The administrator may have blacklisted interfaces
-# or only want zeroconf in a fallback situation
-[ -f /etc/default/zeroconf ] &&
-    . /etc/default/zeroconf
-
-[ -n "$DISABLE" ] && exit 0
-
-for BLACK in $IFBLACKLIST; do
-    case $IFACE in
-	$BLACK)
-	exit 0
-	;;
-    esac
-done
-
-# should we only allocate an address if we do not already have one?
-if [ -n "$FALLBACK" ]; then
-    /bin/ip addr show $IFACE scope global | grep -q "inet"
-    IP=$?
-    if [ $IP -eq 0 ]; then
-        /bin/ip route add 169.254.0.0/16 dev $IFACE
-        exit 0
-    fi
-fi
-
-# otherwise, run if we aren't already going
-if [ ! -r /var/run/zeroconf.$IFACE.pid ]; then
-	/usr/sbin/zeroconf -i $IFACE
-fi
-
-exit 0
diff --git a/meta/recipes-connectivity/zeroconf/zeroconf/zeroconf-default b/meta/recipes-connectivity/zeroconf/zeroconf/zeroconf-default
deleted file mode 100644
index cc07b27..0000000
--- a/meta/recipes-connectivity/zeroconf/zeroconf/zeroconf-default
+++ /dev/null
@@ -1,17 +0,0 @@
-# Default for zeroconf
-
-# disable zeroconf
-# If you want to disable zeroconf completely, uncomment the following line
-# this may be useful if you are debugging zeroconf or starting it manually
-#DISABLE=yes
-
-# black-listed interfaces
-# Interfaces which you never wish to have zeroconf run on should
-# be listed here. e.g. "eth2 wlan1" in a space seperated string
-IFBLACKLIST=""
-
-# fallback only
-# If you would only like a link-local address if you were unable to
-# obtain an address via DHCP then uncomment the following line
-#FALLBACK=yes
-
diff --git a/meta/recipes-connectivity/zeroconf/zeroconf_0.9.bb b/meta/recipes-connectivity/zeroconf/zeroconf_0.9.bb
deleted file mode 100644
index f755940..0000000
--- a/meta/recipes-connectivity/zeroconf/zeroconf_0.9.bb
+++ /dev/null
@@ -1,34 +0,0 @@
-SUMMARY = "IPv4 link-local address allocator"
-DESCRIPTION = "Zeroconf is a program that is used to claim IPv4 \
-link-local addresses. IPv4 link-local addresses are useful when setting \
-up ad-hoc networking between devices without the involvement of a either \
-a DHCP server or network administrator. \
-These addresses are allocated from the 169.254.0.0/16 address range and \
-are normally attached to each Ethernet device in your computer. \
-Addresses are assigned randomly by each host and, in case of collision, \
-both hosts (are supposed to) renumber."
-AUTHOR = "Anand Kumria <wildfire@progsoc.uts.edu.au>"
-HOMEPAGE = "http://www.progsoc.org/~wildfire/zeroconf/"
-LICENSE = "GPLv2+"
-LIC_FILES_CHKSUM = "file://COPYING;md5=4325afd396febcb659c36b49533135d4 \
-                    file://zeroconf.c;beginline=1;endline=13;md5=a5bada96e1e34b08eb7446b28e2630b2"
-SECTION = "net"
-
-PR = "r1"
-
-SRC_URI = "http://www.progsoc.org/~wildfire/zeroconf/download/${BPN}-${PV}.tar.gz \
-           file://compilefix.patch \
-           file://zeroconf-default \
-           file://debian-zeroconf"
-
-SRC_URI[md5sum] = "bdafb16b008ebb5633e4e581f77821d2"
-SRC_URI[sha256sum] = "a8c74df127753e2310fa1e072f3c9ca44a404bb0bbce9cfec7a84c6dff8bec7b"
-
-do_install () {
-	install -d ${D}${sbindir}
-	install -d ${D}${sysconfdir}/network/if-up.d
-	install -d ${D}${sysconfdir}/default
-	install -c -m 755 ${S}/zeroconf ${D}${sbindir}/zeroconf
-	install -c -m 755 ${WORKDIR}/debian-zeroconf ${D}${sysconfdir}/network/if-up.d/zeroconf
-	install -c ${WORKDIR}/zeroconf-default ${D}${sysconfdir}/default/zeroconf
-}
-- 
1.7.9.5




             reply	other threads:[~2012-08-22 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-22 15:50 Paul Eggleton [this message]
2012-08-22 16:11 ` [PATCH] zeroconf: remove - RFC Paul Eggleton
2012-08-22 16:25   ` Burton, Ross
2012-08-22 16:32   ` Koen Kooi
2012-08-22 16:40     ` Richard Purdie
2012-08-22 16:44       ` Burton, Ross
2012-09-03 13:47         ` Paul Eggleton
2012-09-03 13:53           ` Burton, Ross
2012-09-03 14:05             ` Koen Kooi
2012-09-03 14:13               ` Burton, Ross
2012-09-03 14:22                 ` Paul Eggleton
2012-08-22 16:43     ` Paul Eggleton

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=1345650627-3232-1-git-send-email-paul.eggleton@linux.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.