Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Cc: Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-oe][PATCH v3 06/11] p910nd: add version 0.95
Date: Mon, 09 May 2011 14:58:13 +0100	[thread overview]
Message-ID: <1304949493.8000.81.camel@phil-desktop> (raw)
In-Reply-To: <1304872895-21596-6-git-send-email-otavio@ossystems.com.br>

On Sun, 2011-05-08 at 16:41 +0000, Otavio Salvador wrote:
> +++ b/meta-oe/recipes-support/p910nd/files/p910nd.init
> @@ -0,0 +1,31 @@
> +#! /bin/sh
> +
> +test -f /usr/sbin/p910nd || exit 0
> +
> +test -d /var/spool/p910nd || mkdir -p /var/spool/p910nd

This script seems to include a lot of hardwired assumptions about distro
file layout.  Could you make it respect ${sbindir} et al.?

> +    echo -n "Starting p910nd printer daemon: p910nd"
> +    /usr/sbin/p910nd -b -f /dev/usb/lp0 0

... and likewise here, this device node seems a bit over-specific.

> +    echo "."
> +    ;;
> +  stop)
> +    echo -n "Stopping p910nd printer daemon: p910nd"
> +    start-stop-daemon --stop --quiet --exec /usr/sbin/p9100d

This doesn't look like it's going to work: it tries to stop "p9100d" but
that doesn't seem to be the correct name of the executable.

> +do_compile () {
> +	${CC} ${LDFLAGS} -o p910nd p910nd.c
> +}

Shouldn't this also mention $(CFLAGS)?

p.





  reply	other threads:[~2011-05-09 14:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08 16:41 [meta-oe][PATCH v3 01/11] fuse: add version 2.8.5 Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 02/11] ntfs-3g-ntfsprogs: add version 2011.4.12 Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 03/11] setxkbmap: add version 1.2.0 Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 04/11] freerdp: add recipe based on GIT from 2009-03-29 Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 05/11] pixman.inc: use Xorg mirror Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 06/11] p910nd: add version 0.95 Otavio Salvador
2011-05-09 13:58   ` Phil Blundell [this message]
2011-05-09 14:06     ` Otavio Salvador
2011-05-09 14:11       ` Phil Blundell
2011-05-08 16:41 ` [meta-oe][PATCH v3 07/11] libiconv: drop hack since gettext was being inherited Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 08/11] libinih: add git recipe Otavio Salvador
2011-05-08 18:36   ` Koen Kooi
2011-05-08 16:41 ` [meta-oe][PATCH v3 09/11] qt4: drop 4.6 versions Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 10/11] postgresql: update to 8.4.7 since 8.4.4 was unfetchable Otavio Salvador
2011-05-08 16:41 ` [meta-oe][PATCH v3 11/11] qt4: fix 4.7.2 checksum Otavio Salvador
2011-05-08 18:34 ` [meta-oe][PATCH v3 01/11] fuse: add version 2.8.5 Koen Kooi

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=1304949493.8000.81.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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