All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 1/3] Rename package mpc to libmpc
Date: Tue, 22 Jul 2014 10:23:51 +0200	[thread overview]
Message-ID: <53CE1F97.1020300@posteo.de> (raw)
In-Reply-To: <20140721201921.35334933@free-electrons.com>

Dear Thomas,
Dear Gustavo,

On 07/21/2014 08:19 PM, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 21 Jul 2014 13:30:03 -0300, Gustavo Zacarias wrote:
>> On 07/21/2014 11:25 AM, Thomas Petazzoni wrote:
>>
>>> That being said, I would prefer to find a different name for the mpc
>>> package (mpd client) rather than renaming existing packages.
>> +1
>> Renaming it is potentially very problematic for people that use mpc
>> (multiprecision library) for their own projects, mpc would be a
>> completely different thing now and we can't make it legacy either since
>> there would be a new mpc.
>> Just call it mpclient and use a different bool IMHO.
> Agreed. "mpclient" sounds like a good alternative.

okay, I understand that renaming is potentially problematic. But the 
package mpc is not a dependency for any package. gmp is a dependency for 
eight packages, and mpfr for one.

Looking at Debian, Arch, and Fedora, these packages are all named 
libmpc, libgmp, and libmpfr. I liked the idea of having consistent 
package names. And if I am searching for mpc in the menuconfig I find 
the multiprecision library as libmpc and the mpd client as mpc. So it's 
not to difficult to find the right package.

There are dozen of clients for mpd. At least calling the package 
"mpclient" will show my the package when searching for "mpc" in the 
menuconfig.

Btw, is there any rule for duplicate names?

Best regards
J?rg

  reply	other threads:[~2014-07-22  8:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-21 14:12 [Buildroot] [RFC 0/3] Rename of mpc, gmp, mpfr to libmpc, libgmp, libmpfr Jörg Krause
2014-07-21 14:12 ` [Buildroot] [RFC 1/3] Rename package mpc to libmpc Jörg Krause
2014-07-21 14:25   ` Thomas Petazzoni
2014-07-21 16:30     ` Gustavo Zacarias
2014-07-21 18:19       ` Thomas Petazzoni
2014-07-22  8:23         ` Jörg Krause [this message]
2014-07-22 10:20           ` Gustavo Zacarias
2014-07-22 17:02             ` Yann E. MORIN
2014-07-22 18:11               ` Jörg Krause
2014-07-21 14:12 ` [Buildroot] [RFC 2/3] Rename package gmp to libgmp Jörg Krause
2014-07-21 14:12 ` [Buildroot] [RFC 3/3] Rename package mpfr to libmpfr Jörg Krause

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=53CE1F97.1020300@posteo.de \
    --to=jkrause@posteo.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.