Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] introducing transmission bittorrent client
Date: Thu, 23 Sep 2010 00:05:30 +0100	[thread overview]
Message-ID: <20100923000530.049479ea@surf> (raw)
In-Reply-To: <1284884604-2433-1-git-send-email-marcus.osdoba@googlemail.com>

On Sun, 19 Sep 2010 10:23:24 +0200
Marcus Osdoba <marcus.osdoba@googlemail.com> wrote:

> +		IFCONFIG_OUTPUT=`ifconfig $NET_INTERFACE`
> +		IP_ADDR=`expr match "$IFCONFIG_OUTPUT" '.*inet addr:\([0-9]*\.[0-9]*\.[0-9]*\.[0-9]*\).*'`
> +		while [ -z "$IP_ADDR" ]
> +		do
> +			sleep 5
> +			IFCONFIG_OUTPUT=`ifconfig $NET_INTERFACE`
> +			IP_ADDR=`expr match "$IFCONFIG_OUTPUT" '.*inet addr:\([0-9]*\.[0-9]*\.[0-9]*\.[0-9]*\).*'`
> +		done

I'm still not a big fan of this loop. There's really no other solution ?

> +	start)
> +		echo "Starting $DESC" "$NAME..."
> +		do_start
> +		case "$?" in
> +			0) echo "   Start $DESC $NAME: SUCCESS" ;;
> +			*)
> +				echo "   Start $DESC $NAME: FAILED"
> +				exit 3
> +				;;
> +		esac
> +		;;

I don't think we have all this message printing handling in other S??*
scripts, could you simplify this a little bit, for example to make it
similar to package/dropbear/S50dropbear ?

> +ifneq ($(BR2_PACKAGE_TRANSMISSION_REMOTE),y)
> +TRANSMISSION_CONF_OPT += --disable-remote
> +endif

Add a new line here.

> +ifeq ($(BR2_PACKAGE_TRANSMISSION_REMOTE),y)
> +define TRANSMISSION_INITDSKRIPT_INSTALL

INITDSKRIPT looks strange. INIT_SCRIPT instead ?

> +	# install start/stop script
> +	$(call MESSAGE,"Installing S92transmission init script")
> +	if [ ! -f $(TARGET_DIR)/etc/init.d/S92transmission ]; then \
> +		$(INSTALL) -m 0755 -D package/transmission/S92transmission \
> +		$(TARGET_DIR)/etc/init.d/S92transmission; \
> +	fi
> +	$(Q)touch $@

The touch here is not needed.

Otherwise, looks good to me. Care to fix these and resend an updated
version ?

Thanks a lot for all your efforts and your patience!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2010-09-22 23:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19  8:23 [Buildroot] [PATCH] introducing transmission bittorrent client Marcus Osdoba
2010-09-19  9:53 ` Marcus Osdoba
2010-09-21  2:00   ` Kelvin Cheung
2010-09-22 20:26     ` Marcus Osdoba
2010-09-22 23:06       ` Thomas Petazzoni
2010-09-27 21:46     ` Marcus Osdoba
2010-09-29  8:22       ` Thomas Petazzoni
2010-09-22 23:05 ` Thomas Petazzoni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-09-13 18:07 [Buildroot] resend transmission bittorrent client after 1st review by Thomas Marcus Osdoba
2010-09-13 18:07 ` [Buildroot] [PATCH] introducing transmission bittorrent client Marcus Osdoba
2010-09-09 20:28 [Buildroot] transmission better choice over ctorrent according to users voices Marcus Osdoba
2010-09-09 20:28 ` [Buildroot] [PATCH] introducing transmission bittorrent client Marcus Osdoba
2010-09-10  5:07   ` Belisko Marek
2010-09-10  8:10     ` Thomas Petazzoni
2010-09-10  8:15       ` Belisko Marek
2010-09-11 16:32         ` Marcus Osdoba
2010-09-10  6:55   ` Thomas Petazzoni

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=20100923000530.049479ea@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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