From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/6] hdmiservice: new package
Date: Tue, 13 Nov 2012 12:06:38 +0100 [thread overview]
Message-ID: <20121113120638.6d605ebf@skate> (raw)
In-Reply-To: <50A228E9.70507@calao-systems.com>
On Tue, 13 Nov 2012 12:03:05 +0100, Gr?gory Hermant wrote:
> Hi thomas,
>
> Le 12/11/2012 19:34, Thomas Petazzoni a ?crit :
> > Dear Gregory Hermant,
> >
> > On Mon, 12 Nov 2012 18:41:37 +0100, Gregory Hermant wrote:
> >>
> >> Signed-off-by: Gregory Hermant <gregory.hermant@calao-systems.com>
> >> ---
> >> package/Config.in | 1 +
> >> package/hdmiservice/Config.in | 10 +++++++++
> >> package/hdmiservice/hdmiservice.mk | 43 ++++++++++++++++++++++++++++++++++++
> >
> > Is this software something generic, or very specific to the Snowball
> > platform? I am worried by the package name that is way too generic for
> > something that looks board specific. It seems to be tied to a very
> > custom graphics driver.
>
> Yes it is specific to the snowball.
> What do you suggest to manage this package ?
Even though we generally prefer to use the upstream name for the
Buildroot package, in this case the upstream name is way too generic.
The package should probably be named snowball-hdmiservice for example.
> > Any reason not to use the 'make install' target which apparently does
> > the right thing?
> >
> Not really. I just keep a similar syntax as staging part.
> What do you recommend ?
Why not using make install for both the target and staging
installations?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-11-13 11:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 17:41 [Buildroot] [PATCH v2 0/6] Add support for the snowball board Gregory Hermant
2012-11-12 17:41 ` [Buildroot] [PATCH v2 1/6] hdmiservice: new package Gregory Hermant
2012-11-12 18:34 ` Thomas Petazzoni
2012-11-13 11:03 ` Grégory Hermant
2012-11-13 11:06 ` Thomas Petazzoni [this message]
2012-11-12 17:41 ` [Buildroot] [PATCH v2 2/6] ux500-firmware: " Gregory Hermant
2012-11-12 21:44 ` Arnout Vandecappelle
2012-11-12 17:41 ` [Buildroot] [PATCH v2 3/6] Add board files for snowball Gregory Hermant
2012-11-12 18:37 ` Thomas Petazzoni
2012-11-13 11:03 ` Grégory Hermant
2012-11-13 21:18 ` Arnout Vandecappelle
2012-11-12 17:41 ` [Buildroot] [PATCH v2 4/6] Add init script files for snowball board Gregory Hermant
2012-11-12 21:45 ` Arnout Vandecappelle
2012-11-12 17:41 ` [Buildroot] [PATCH v2 5/6] bluez-utils: add cg2900 support " Gregory Hermant
2012-11-12 21:47 ` Arnout Vandecappelle
2012-11-12 17:41 ` [Buildroot] [PATCH v2 6/6] Add config file for the " Gregory Hermant
2012-11-12 21:53 ` Arnout Vandecappelle
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=20121113120638.6d605ebf@skate \
--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