From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] package/libedit2: new package
Date: Wed, 15 May 2013 09:01:26 +0200 [thread overview]
Message-ID: <519332C6.9080509@mind.be> (raw)
In-Reply-To: <20130514224214.GB8043@free.fr>
On 15/05/13 00:42, Yann E. MORIN wrote:
> Arnout, All,
>
> On 2013-05-15 00:27 +0200, Arnout Vandecappelle spake thusly:
>> Why is it called libedit2? Both NetBSD and Debian call it libedit...
>
> Debian actually calls it:
> libedit2
> libedit-dev
> See: http://packages.debian.org/search?keywords=libedit
The digit after the libxxx binary is the library soname, which isn't
relevant for us. You should consider the source package name as the
upstream name.
Putting a digit behind the name should only be necessary for major
non-backward-compatible API changes, like qt5 or gstreamer1.
Regards,
Arnout
[snip]
--
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
next prev parent reply other threads:[~2013-05-15 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 21:45 [Buildroot] [pull request v8 (for next)] Pull request for branch yem-new-packages Yann E. MORIN
2013-05-14 21:45 ` [Buildroot] [PATCH 1/3] package/pmake: force argv[0]=${0} in the pmake wrapper Yann E. MORIN
2013-05-30 20:58 ` Peter Korsgaard
2013-05-14 21:45 ` [Buildroot] [PATCH 2/3] package/libedit2: new package Yann E. MORIN
2013-05-14 22:27 ` Arnout Vandecappelle
2013-05-14 22:42 ` Yann E. MORIN
2013-05-15 7:01 ` Arnout Vandecappelle [this message]
2013-05-15 20:56 ` Yann E. MORIN
2013-05-30 21:03 ` Peter Korsgaard
2013-05-14 21:45 ` [Buildroot] [PATCH 3/3] package/snappy: " Yann E. MORIN
2013-05-30 21:04 ` Peter Korsgaard
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=519332C6.9080509@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 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.