Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steve James <ste@junkomatic.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] leveldb: new package
Date: Thu, 8 Jan 2015 12:50:56 +0000	[thread overview]
Message-ID: <201501081250.56410.ste@junkomatic.net> (raw)
In-Reply-To: <20150108132719.02d06610@free-electrons.com>

On Thursday 08 Jan 2015 12:27:19 Thomas Petazzoni wrote:
--snip--

> Well, Buildroot is re-using kconfig directly from the Linux kernel
> sources. So we haven't defined the kconfig language, and we don't want
> to change it specifically for Buildroot.

As I thought. I'll get used to it.

--snip--

> If you don't use a full path and do:
> 
> 	$(INSTALL) -D $(@D)/foo $(STAGING_DIR)/usr/lib
> 
> and $(STAGING_DIR)/usr/lib doesn't already exist as a directory, then a
> file named $(STAGING_DIR)/usr/lib will be created, with the contents of
> $(@D)/foo. Cleary not what we want.

I would ordinarily create destination directories first, but I hadn't in this 
case, so good point.

> > > It would be good to add a comment above all these installation rules to
> > > indicate that the leveldb build system doesn't provide any "make
> > > install" rule.
> > 
> > Or better: I'll add the missing install recipe to the Makefile.
> 
> Indeed.
> 
> However, I looked quickly at the contribution process for leveldb and
> it's a bit annoying: you have to sign a CLA to assign the copyright of
> your contributions. Or hopefully they might consider those
> contributions as small enough to not be copyrightable, and avoid the
> CLA hassle. I'll let you handle that with upstream.

Yes I saw that too. How very annoying. I'm reluctant to put my name on a 
Google License Agreement just to tweak a Makefile. I see they even want my 
address and phone number. Hmm.

Whether they accept it upstream or not, I think patching the install recipe 
into the leveldb Makefile is a more correct solution and will be better for 
Buildroot.

Steve.

      reply	other threads:[~2015-01-08 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 14:47 [Buildroot] [PATCH v4] leveldb: new package Steve James
2015-01-07  9:12 ` Thomas Petazzoni
2015-01-08 12:09   ` Steve James
2015-01-08 12:27     ` Thomas Petazzoni
2015-01-08 12:50       ` Steve James [this message]

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=201501081250.56410.ste@junkomatic.net \
    --to=ste@junkomatic.net \
    --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