Skip to contentSkip to conversation

libgpiod: drop support for 0.3.3

PATCH In review Bartosz Golaszewski 2 participants 5 messages Sep 17, 2020 – Sep 18, 2020 1 message not in the archive

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 libgpiod: drop support for 0.3.3

From: Bartosz Golaszewski <[email protected]>

I no longer support the v0.x.y series. Remove the recipe for v0.3.3. While at it: the tests PACKAGECONFIG is duplicated so remove one instance.

---
 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb | 8 --------
 meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb | 2 --
 2 files changed, 10 deletions(-)
 delete mode 100644 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb
meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb deleted +0 -8
deleted file mode 100644
index c4d2bddf4..000000000
@@ -1,8 +0,0 @@
-require libgpiod.inc
-
-PACKAGECONFIG ?= ""
-
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
-SRC_URI[md5sum] = "2aa1e1a80c3c919ae142ab9a55fb59ca"
-SRC_URI[sha256sum] = "b773e557af1a497f786825462a776b7bf90168e67ee0a5bc5d2473a5674dc38c"
meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb +0 -2
index a9a462866..b5a64a554 100644
@@ -9,8 +9,6 @@ SRC_URI[sha256sum] = "f1cda2789e6a13a92aefc012a76e5a7cc57a1b402d66f71df8719ee314
 PACKAGECONFIG ?= "cxx"
 
 PACKAGECONFIG[cxx] = "--enable-bindings-cxx,--disable-bindings-cxx"
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
 PACKAGECONFIG[python3] = "--enable-bindings-python,--disable-bindings-python,python3"
 
 inherit python3native
Signature · 1 line
2.26.1
#1 lore raw

is 1.4.4 backward compatible?

Quoted 44 lines · Bartosz Golaszewski

From: Bartosz Golaszewski <[email protected]>

I no longer support the v0.x.y series. Remove the recipe for v0.3.3. While at it: the tests PACKAGECONFIG is duplicated so remove one instance.

---
 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb | 8 --------
 meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb | 2 --
 2 files changed, 10 deletions(-)
 delete mode 100644 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb
meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb deleted +0 -8
deleted file mode 100644
index c4d2bddf4..000000000
@@ -1,8 +0,0 @@
-require libgpiod.inc
-
-PACKAGECONFIG ?= ""
-
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
-SRC_URI[md5sum] = "2aa1e1a80c3c919ae142ab9a55fb59ca"
-SRC_URI[sha256sum] = "b773e557af1a497f786825462a776b7bf90168e67ee0a5bc5d2473a5674dc38c"
meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb +0 -3
index a9a462866..b5a64a554 100644
@@ -9,8 +9,6 @@ SRC_URI[sha256sum] = "f1cda2789e6a13a92aefc012a76e5a7cc57a1b402d66f71df8719ee314
 PACKAGECONFIG ?= "cxx"
 
 PACKAGECONFIG[cxx] = "--enable-bindings-cxx,--disable-bindings-cxx"
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
 PACKAGECONFIG[python3] = "--enable-bindings-python,--disable-bindings-python,python3"
 
 inherit python3native
--

2.26.1

#2 lore raw
Quoted 44 lines · Khem Raj

is 1.4.4 backward compatible?

Quoted 40 lines · Bartosz Golaszewski

From: Bartosz Golaszewski <[email protected]>

I no longer support the v0.x.y series. Remove the recipe for v0.3.3. While at it: the tests PACKAGECONFIG is duplicated so remove one instance.

---
 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb | 8 --------
 meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb | 2 --
 2 files changed, 10 deletions(-)
 delete mode 100644 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb
meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb deleted +0 -8
deleted file mode 100644
index c4d2bddf4..000000000
@@ -1,8 +0,0 @@
-require libgpiod.inc
-
-PACKAGECONFIG ?= ""
-
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
-SRC_URI[md5sum] = "2aa1e1a80c3c919ae142ab9a55fb59ca"
-SRC_URI[sha256sum] = "b773e557af1a497f786825462a776b7bf90168e67ee0a5bc5d2473a5674dc38c"
meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb +0 -2
index a9a462866..b5a64a554 100644
@@ -9,8 +9,6 @@ SRC_URI[sha256sum] = "f1cda2789e6a13a92aefc012a76e5a7cc57a1b402d66f71df8719ee314
 PACKAGECONFIG ?= "cxx"
 
 PACKAGECONFIG[cxx] = "--enable-bindings-cxx,--disable-bindings-cxx"
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
 PACKAGECONFIG[python3] = "--enable-bindings-python,--disable-bindings-python,python3"
 
Quoted 4 lines
Quoted 4 lines
meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb +0 -1
 inherit python3native
--

2.26.1

No, it was a major release with a new API but 0.x was never meant to even be stable, it was largely a development series before we nailed down a good interface and released v1.0.

Bart

#4 lore raw
In reply to a message not in the archive
Quoted 46 lines · Bartosz Golaszewski
Quoted 44 lines · Khem Raj

is 1.4.4 backward compatible?

Quoted 40 lines · Bartosz Golaszewski

From: Bartosz Golaszewski <[email protected]>

I no longer support the v0.x.y series. Remove the recipe for v0.3.3. While at it: the tests PACKAGECONFIG is duplicated so remove one instance.

---
 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb | 8 --------
 meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb | 2 --
 2 files changed, 10 deletions(-)
 delete mode 100644 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb
meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb deleted +0 -8
deleted file mode 100644
index c4d2bddf4..000000000
@@ -1,8 +0,0 @@
-require libgpiod.inc
-
-PACKAGECONFIG ?= ""
-
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
-SRC_URI[md5sum] = "2aa1e1a80c3c919ae142ab9a55fb59ca"
-SRC_URI[sha256sum] = "b773e557af1a497f786825462a776b7bf90168e67ee0a5bc5d2473a5674dc38c"
meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb +0 -2
index a9a462866..b5a64a554 100644
@@ -9,8 +9,6 @@ SRC_URI[sha256sum] = "f1cda2789e6a13a92aefc012a76e5a7cc57a1b402d66f71df8719ee314
 PACKAGECONFIG ?= "cxx"
 
 PACKAGECONFIG[cxx] = "--enable-bindings-cxx,--disable-bindings-cxx"
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
 PACKAGECONFIG[python3] = "--enable-bindings-python,--disable-bindings-python,python3"
 
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb +0 -1
 inherit python3native
--

2.26.1

No, it was a major release with a new API but 0.x was never meant to even be stable, it was largely a development series before we nailed down a good interface and released v1.0.

OK, perhaps a deprecation notice for a release might have been better, but since you maintain this recipe and
perhaps has better idea of its users, I will defer that judgment to you.

Quoted 2 lines

Bart

#5 lore raw
Quoted 58 lines · Khem Raj
Quoted 46 lines · Bartosz Golaszewski
Quoted 44 lines · Khem Raj

is 1.4.4 backward compatible?

Quoted 40 lines · Bartosz Golaszewski

From: Bartosz Golaszewski <[email protected]>

I no longer support the v0.x.y series. Remove the recipe for v0.3.3. While at it: the tests PACKAGECONFIG is duplicated so remove one instance.

---
 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb | 8 --------
 meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb | 2 --
 2 files changed, 10 deletions(-)
 delete mode 100644 meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb
meta-oe/recipes-support/libgpiod/libgpiod_0.3.3.bb deleted +0 -8
deleted file mode 100644
index c4d2bddf4..000000000
@@ -1,8 +0,0 @@
-require libgpiod.inc
-
-PACKAGECONFIG ?= ""
-
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
-SRC_URI[md5sum] = "2aa1e1a80c3c919ae142ab9a55fb59ca"
-SRC_URI[sha256sum] = "b773e557af1a497f786825462a776b7bf90168e67ee0a5bc5d2473a5674dc38c"
meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb +0 -2
index a9a462866..b5a64a554 100644
@@ -9,8 +9,6 @@ SRC_URI[sha256sum] = "f1cda2789e6a13a92aefc012a76e5a7cc57a1b402d66f71df8719ee314
 PACKAGECONFIG ?= "cxx"
 
 PACKAGECONFIG[cxx] = "--enable-bindings-cxx,--disable-bindings-cxx"
-PACKAGECONFIG[tests] = "--enable-tests,--disable-tests,kmod udev"
-
 PACKAGECONFIG[python3] = "--enable-bindings-python,--disable-bindings-python,python3"
 
Quoted 8 lines
Quoted 4 lines
Quoted 4 lines
meta-oe/recipes-support/libgpiod/libgpiod_1.4.4.bb +0 -1
 inherit python3native
--

2.26.1

No, it was a major release with a new API but 0.x was never meant to even be stable, it was largely a development series before we nailed down a good interface and released v1.0.

Quoted 6 lines

OK, perhaps a deprecation notice for a release might have been better, but since you maintain this recipe and
perhaps has better idea of its users, I will defer that judgment to you.

Quoted 2 lines

Bart

Yes, it's fine - this branch hasn't received any updates for over two years. It doesn't even support all kernel features. I maintain the library itself and don't have any intention of bringing v0.3 back to life.

Thanks,
Bartosz