From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/dvb-apps: new package
Date: Fri, 28 Dec 2012 23:30:21 +0100 [thread overview]
Message-ID: <87ehi9yflu.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <d4ede3beb81857dfef0587def373e943f2a6100d.1356731295.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Fri, 28 Dec 2012 22:48:34 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Yann> We just need the transponders data, so we just install those.
Long term I think it would be good to make this a user visible package,
and have sub options for what kind of transponder data you want to
install, as it's fairly big (~3.4MB).
Yann> +define DVB_APPS_INSTALL_TARGET_CMDS
Yann> + mkdir -p $(TARGET_DIR)/usr/share/dvb-apps/scan/atsc
Yann> + mkdir -p $(TARGET_DIR)/usr/share/dvb-apps/scan/dvb-c
Yann> + mkdir -p $(TARGET_DIR)/usr/share/dvb-apps/scan/dvb-s
Yann> + mkdir -p $(TARGET_DIR)/usr/share/dvb-apps/scan/dvb-t
Yann> + $(INSTALL) -D $(@D)/util/scan/atsc/* $(TARGET_DIR)/usr/share/dvb-apps/scan/atsc
install -D expects you to name the destination file name, which doesn't
make sense here, so I rewrote the install step to use a shell loop and
not use the -D option.
Committed with that change, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-12-28 22:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 21:48 [Buildroot] [pull request] Pull request for branch yem-tvheadend Yann E. MORIN
2012-12-28 21:48 ` [Buildroot] [PATCH 1/2] package/dvb-apps: new package Yann E. MORIN
2012-12-28 22:30 ` Peter Korsgaard [this message]
2012-12-28 22:40 ` Yann E. MORIN
2012-12-28 21:48 ` [Buildroot] [PATCH 2/2] package/tvheadend: " Yann E. MORIN
-- strict thread matches above, loose matches on Subject: below --
2012-12-28 18:42 [Buildroot] [pull request] Pull request for branch yem-tvheadend Yann E. MORIN
2012-12-28 18:42 ` [Buildroot] [PATCH 1/2] package/dvb-apps: new package Yann E. MORIN
2012-12-28 19:45 ` 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=87ehi9yflu.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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