[PATCH] i2c-tools: Remove superseded i2c-tools 3.0.1.

[PATCH] i2c-tools: Remove superseded i2c-tools 3.0.1.

[Robert P. J. Day]

Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

---

  whoops, ignore earlier patch, i forgot to remove the entry from
checksums.ini.

diff --git a/conf/checksums.ini b/conf/checksums.ini
index 8252329..8a66ed1 100644
--- a/conf/checksums.ini
+++ b/conf/checksums.ini
@@ -12010,10 +12010,6 @@ sha256=1019b3fbeb3e7e2d0c8faf81191e722bfabc714ee03ec08703faf91dab443b64
 md5=01f5cc3adbe9d161cf8e1855cec4fa15
 sha256=9a9b7092f2e48786e8f83e5bef99fd31988f87140ad9ca840583f91b3623d628

-[http://dl.lm-sensors.org/i2c-tools/releases/i2c-tools-3.0.1.tar.bz2]
-md5=0f5c7ce5fd3c65113909db0ef3a3a8c8
-sha256=8cf39f7c447b0b8f7a24eaed243ad4d8c654c2e94a146a796dba9ed08e857209
-
 [http://dl.lm-sensors.org/i2c-tools/releases/i2c-tools-3.0.2.tar.bz2]
 md5=b546345ac19db56719dea6b8199f11e0
 sha256=0b4d6455a30a3264a60b4d3be55855d996d52ea4f162a2f04ffff378e24f98a2
diff --git a/recipes/i2c-tools/i2c-tools_3.0.1.bb b/recipes/i2c-tools/i2c-tools_3.0.1.bb
deleted file mode 100644
index c8ea32a..0000000
--- a/recipes/i2c-tools/i2c-tools_3.0.1.bb
+++ /dev/null
@@ -1,12 +0,0 @@
-DESCRIPTION = "Set of i2c tools for linux"
-SECTION = "base"
-LICENSE = "GPL"
-
-SRC_URI = "http://dl.lm-sensors.org/i2c-tools/releases/i2c-tools-${PV}.tar.bz2"
-
-inherit autotools
-
-do_compile_prepend() {
-        sed -i 's_/usr/local_/usr_' Makefile
-        sed -i 's_CC\t:= gcc_CC\t:= ${CC}_' Makefile
-}


========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

Re: [PATCH] i2c-tools: Remove superseded i2c-tools 3.0.1.

[Florian Boor]

Hi,

Robert P. J. Day schrieb:
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>

I do not agree on this. There is no way to make sure people are not using it.
Even if it is unlikely the new release might break for some of our users or just
rely on something that is not available for everyone.
Apart from this I do not see much of a reason for removing it at all.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de
                                        http://www.kernelconcepts.de/en

Re: [PATCH] i2c-tools: Remove superseded i2c-tools 3.0.1.

[Robert P. J. Day]

On Mon, 16 Nov 2009, Florian Boor wrote:

> Hi,
>
> Robert P. J. Day schrieb:
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> I do not agree on this. There is no way to make sure people are not
> using it. Even if it is unlikely the new release might break for
> some of our users or just rely on something that is not available
> for everyone. Apart from this I do not see much of a reason for
> removing it at all.

  based on a couple earlier comments, i'll agree.  so what's the
proper protocol for adding a newer version?  just submit a patch that
*adds* the appropriate content while leaving the current version info
in place?  i can easily submit a patch for that.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================

Re: [PATCH] i2c-tools: Remove superseded i2c-tools 3.0.1.

[Florian Boor]

Hi,

Robert P. J. Day schrieb:
>   based on a couple earlier comments, i'll agree.  so what's the
> proper protocol for adding a newer version?  just submit a patch that
> *adds* the appropriate content while leaving the current version info
> in place?  i can easily submit a patch for that.

yes right, just submit a patch that adds the new one.

Greetings

Florian

-- 
The dream of yesterday                  Florian Boor
is the hope of today                    Tel: +49 271-771091-15
and the reality of tomorrow.            Fax: +49 271-771091-19
[Robert Hutchings Goddard, 1904]        florian.boor@kernelconcepts.de
                                        http://www.kernelconcepts.de/en

Re: [PATCH] i2c-tools: Remove superseded i2c-tools 3.0.1.

[Robert P. J. Day]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1348 bytes --]

On Mon, 16 Nov 2009, Florian Boor wrote:

> Hi,
>
> Robert P. J. Day schrieb:
> > Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> I do not agree on this. There is no way to make sure people are not
> using it. Even if it is unlikely the new release might break for
> some of our users or just rely on something that is not available
> for everyone. Apart from this I do not see much of a reason for
> removing it at all.

  by the way, i did check the changelog first to see if the
enhancements were useful enough to warrant upgrading.  the changelog:

http://linux.softpedia.com/progChangelog/I2C-Tools-Changelog-31650.html

What's new in I2C Tools 3.0.2:
· Error handling has been improved.
· Buses can now be passed by name.
· A compatibility issue with perl 5.10.0 has been fixed.

that struck me as sufficiently useful to warrant an upgrade, but maybe
not.

rday
--

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================