From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Aurelien Jarno <aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org>
Subject: Re: i2c-tools: Discussion points about future library
Date: Wed, 4 Apr 2012 18:41:58 +0100 [thread overview]
Message-ID: <20120404174158.GA19773@sirena.org.uk> (raw)
In-Reply-To: <20120404160113.2295c636-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
On Wed, Apr 04, 2012 at 04:01:13PM +0200, Jean Delvare wrote:
> First point is the name of the library. My original intent was to name
> it libi2c-dev, because the library is essentially a front-end to the
> i2c-dev kernel driver, and also because this is what Debian named their
> package currently containing the (i2c-tools flavor of)
> <linux/i2c-dev.h>. However Aur??lien Jarno suggested that libi2c would
> be just as fine, and easier/shorter. I am mostly convinced by now. I am
> curious if anyone wants to express an opinion on the matter?
FWIW the Debian convention is that the source package of a library is
called libfoo building packages libfoo-dev with the headers and .so
symlink to link against (or .a for a static library) and libfooN with
the runtime in it (where N is the soname).
next prev parent reply other threads:[~2012-04-04 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 14:01 i2c-tools: Discussion points about future library Jean Delvare
[not found] ` <20120404160113.2295c636-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-04-04 17:41 ` Mark Brown [this message]
[not found] ` <20120404174158.GA19773-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2012-04-04 19:23 ` Jean Delvare
[not found] ` <20120404212323.59053a1f-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-04-04 19:41 ` Martin Mokrejs
[not found] ` <4F7CA3D4.8000104-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@public.gmane.org>
2012-04-04 19:42 ` Martin Mokrejs
2012-04-05 7:49 ` Jean Delvare
[not found] ` <20120405094910.1dcc4779-R0o5gVi9kd7kN2dkZ6Wm7A@public.gmane.org>
2012-04-05 8:04 ` Wolfram Sang
2012-04-05 9:42 ` Martin Mokrejs
[not found] ` <4F7D68F2.4040106-08dBlVkRsZWoiTQjSSYKZesEoJ4y9sgM@public.gmane.org>
2012-04-05 11:50 ` Jean Delvare
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=20120404174158.GA19773@sirena.org.uk \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=aurelien-rXXEIb44qovR7s880joybQ@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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