Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libnfc-llcp: rename to libllcp and bump version
Date: Fri, 10 Jan 2014 13:19:05 +0000	[thread overview]
Message-ID: <52CFF349.1080103@imgtec.com> (raw)
In-Reply-To: <52CF8D87.20000@mind.be>

On 01/10/2014 06:04 AM, Arnout Vandecappelle wrote:
> On 09/01/14 18:07, Vicente Olivert Riera wrote:
>> This package has been renamed upstream to libllcp.
>
>   This is not sufficient reason to rename the package in buildroot as
> well. Renaming makes it difficult for people to follow buildroot
> upstream with their configurations.

The real reason to do this is because doing a version bump you will fix 
a compilation error due to libnfc-llcp not being compatible with libnfc. 
So, when you try to do a version bump, you notice that upstream has 
renamed the package, so..., why not do it altogether?

>   Also, if any existing symbol is removed (or renamed), entries have to
> be added to Config.in.legacy. This makes is slightly easier for users to
> maintain buildroot configurations, but it's still annoying so renaming
> of symbols should be done with care.

You are writing a comment for the first version patch. The last one is 
the V3 patch which already modifies Config.in.legacy to do this.

>
>   It _is_ an option to still rename it in the menu. I'm not entirely
> sure what should be done with the alphabetical ordering in that case -
> probably follow the visible name, not the internal name.
>
>   Regards,
>   Arnout
>
>> Also, the current
>> package we have in Buildroot fails to compile due to a version bump of
>> it's main dependence, libnfc. A version bump is required because this
>> package has been adapted upstream to work with libnfc-1.7.0-rc6.
>>
>> Signed-off-by: Vicente Olivert Riera<Vincent.Riera@imgtec.com>
>> ---
>>   package/Config.in                          |    2 +-
>>   package/{libnfc-llcp => libllcp}/Config.in |    6 +++---
>>   package/libllcp/libllcp.mk                 |   15 +++++++++++++++
>>   package/libnfc-llcp/libnfc-llcp.mk         |   15 ---------------
>>   4 files changed, 19 insertions(+), 19 deletions(-)
>>   rename package/{libnfc-llcp => libllcp}/Config.in (56%)
>>   create mode 100644 package/libllcp/libllcp.mk
>>   delete mode 100644 package/libnfc-llcp/libnfc-llcp.mk
>
>


-- 
Vincent

  reply	other threads:[~2014-01-10 13:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09 17:07 [Buildroot] [PATCH] libnfc-llcp: rename to libllcp and bump version Vicente Olivert Riera
2014-01-09 17:42 ` Yann E. MORIN
2014-01-09 17:43 ` Baruch Siach
2014-01-09 23:23 ` Thomas Petazzoni
2014-01-10 10:07   ` Vicente Olivert Riera
2014-01-10  6:04 ` Arnout Vandecappelle
2014-01-10 13:19   ` Vicente Olivert Riera [this message]
2014-01-11  0:47   ` 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=52CFF349.1080103@imgtec.com \
    --to=vincent.riera@imgtec.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