Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] PACKAGE_USERS does not work
Date: Fri, 11 Jul 2014 22:37:33 +0200	[thread overview]
Message-ID: <20140711203733.GE3739@free.fr> (raw)
In-Reply-To: <53BFE547.70600@posteo.de>

J?rg, All,

You said in another mail that you'd be sending a patch to add this
package. Thanks!

So, here is my preliminary review of the .mk file:

On 2014-07-11 15:23 +0200, J?rg Krause spake thusly:
>   ################################################################################
>   #
>   # upmpdcli
>   #
>   ################################################################################
> 
>   UPMPDCLI_VERSION = 0.7.1
>   UPMPDCLI_SITE = http://www.lesbonscomptes.com/upmpdcli/downloads
>   UPMPDCLI_LICENSE = GPLv2
>   UPMPDCLI_LICENSE_FILES = LICENSE
>   UPMPDCLI_INSTALL_STAGING = YES

Wh yinstall in staging? As far as I can see, this installs a program,
not a library, right? We install in staging only when the package
installs one (or more) libraries.

>   UPMPDCLI_INSTALL_TARGET = YES

Not needed, that's the default.

>   UPMPDCLI_AUTORECONF = YES

Why do you autoreconf? It is not normally needed. If it is needed, add a
comment stating why. See the existing packages for hints. ;-)

>   UPMPDCLI_CONF_OPT = --prefix=/usr

Nope, that's already taken care of by the autotools-package
infrastructure.

>   UPMPDCLI_DEPENDENCIES = host-pkgconf
>   UPMPDCLI_DEPENDENCIES += libupnp
>   UPMPDCLI_DEPENDENCIES += libmpdclient

Please, put the dependencies on a single. If it does not fit in 80-char,
then use continuation lines, like:

    UPMPDCLI_DEPENDENCIES = host-pkgconf libupnp libmpdclient tooloong \
        more-depndencies on-this-line

BTW, it also depends on expat.

>   define UPMPDCLI_USERS
>       upmpdcli -1 upmpdcli -1 * - - -
>   endef

Do you really need a specific user for running upmpdcli?

Also, would it need to belong to the audio group (as an additional
group)? (even though it does not directly render audio)

>   define UPMPDCLI_INSTALL_INIT_SYSV
>       $(INSTALL) -m 0755 package/upmpdcli/S99upmpdcli $(TARGET_DIR)/etc/init.d/
>   endef

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  parent reply	other threads:[~2014-07-11 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-11  8:57 [Buildroot] PACKAGE_USERS does not work Jörg Krause
2014-07-11 11:41 ` Johan Oudinet
2014-07-11 13:23   ` Jörg Krause
2014-07-11 16:21     ` Johan Oudinet
2014-07-11 17:00     ` Arnout Vandecappelle
2014-07-11 17:28       ` Yann E. MORIN
2014-07-11 18:12         ` Jörg Krause
2014-07-11 17:26     ` Yann E. MORIN
2014-07-11 20:37     ` Yann E. MORIN [this message]
2014-07-14 10:09       ` Jörg Krause
2014-07-14 10:16         ` Yann E. MORIN

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=20140711203733.GE3739@free.fr \
    --to=yann.morin.1998@free.fr \
    --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