Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/7] General LTTng packages maintenance
Date: Sat, 07 Mar 2015 02:02:20 +0100	[thread overview]
Message-ID: <54FA4E1C.9080909@mind.be> (raw)
In-Reply-To: <20150306233246.11b83af2@free-electrons.com>

On 06/03/15 23:32, Thomas Petazzoni wrote:
> Dear Philippe Proulx,
> 
> On Fri,  6 Mar 2015 12:35:50 -0500, Philippe Proulx wrote:
> 
>>   lttng-libust: rename package to lttng-ust
>>   lttng-babeltrace: rename package to babeltrace
> 
> To be honest, I am not sure about those ones. Renaming packages causes
> backward compatibility problems (that should be handled by adding the
> relevant entries in Config.in.legacy, which your patches is not doing),
> so renaming just for the sake of renaming, I'm not sure.

 For lttng-libust, I really think it's silly to rename it. Nobody will be
bothered by it.

 Babeltrace on the other hand is more defendable. Are there any other packages
that we carry that produces traces that can be read by babeltrace?

 Note also that there always has been pushback from Peter against gratuitous
renaming.

> 
> Since they lack the Config.in.legacy handling, I'll mark your patches
> as Changes Requested in our patch tracking system. When you'll resubmit
> them, I'll try to gather the opinion of other Buildroot developers to
> see what they think.

 Not only legacy handling, but also alphabetical ordering in package/Config.in.


 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-03-07  1:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06 17:35 [Buildroot] [PATCH 0/7] General LTTng packages maintenance Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 1/7] liburcu: bump to version 0.8.6 Philippe Proulx
2015-03-06 22:21   ` Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 2/7] lttng-tools: bump to version 2.6.0 Philippe Proulx
2015-03-06 22:21   ` Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 3/7] lttng-libust: " Philippe Proulx
2015-03-06 22:24   ` Thomas Petazzoni
2015-03-07  0:33     ` Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 4/7] lttng-modules: " Philippe Proulx
2015-03-06 22:28   ` Thomas Petazzoni
2015-03-07  0:35     ` Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 5/7] lttng-babeltrace: update Config.in's help Philippe Proulx
2015-03-06 22:30   ` Thomas Petazzoni
2015-03-06 17:35 ` [Buildroot] [PATCH 6/7] lttng-libust: rename package to lttng-ust Philippe Proulx
2015-03-06 17:35 ` [Buildroot] [PATCH 7/7] lttng-babeltrace: rename package to babeltrace Philippe Proulx
2015-03-06 22:32 ` [Buildroot] [PATCH 0/7] General LTTng packages maintenance Thomas Petazzoni
2015-03-07  1:02   ` Arnout Vandecappelle [this message]
2015-03-07  7:59     ` Thomas Petazzoni
2015-03-07 20:50       ` Philippe Proulx

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=54FA4E1C.9080909@mind.be \
    --to=arnout@mind.be \
    --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