Hello community, here is the log from the commit of package 96BoardsGPIO for openSUSE:Factory checked in at 2018-02-20 17:56:15 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/96BoardsGPIO (Old) and /work/SRC/openSUSE:Factory/.96BoardsGPIO.new (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "96BoardsGPIO" Tue Feb 20 17:56:15 2018 rev:3 rq:578263 version:0.0+git.20170225 Changes: -------- --- /work/SRC/openSUSE:Factory/96BoardsGPIO/96BoardsGPIO.changes 2018-02-07 18:43:05.391472939 +0100 +++ /work/SRC/openSUSE:Factory/.96BoardsGPIO.new/96BoardsGPIO.changes 2018-02-20 17:56:21.111706459 +0100 @@ -1,0 +2,5 @@ +Sun Feb 18 12:06:40 UTC 2018 - jeng...@inai.de + +- Compact description. + +------------------------------------------------------------------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ 96BoardsGPIO.spec ++++++ --- /var/tmp/diff_new_pack.eBJa8b/_old 2018-02-20 17:56:22.679650003 +0100 +++ /var/tmp/diff_new_pack.eBJa8b/_new 2018-02-20 17:56:22.683649859 +0100 @@ -23,7 +23,7 @@ Summary: A library to make GPIO use across 96Boards uniform License: LGPL-2.1 Group: Development/Libraries/C and C++ -URL: https://github.com/96boards/96BoardsGPIO +Url: https://github.com/96boards/96BoardsGPIO Source: %{name}-%{version}.tar.xz Patch0: 96BoardsGPIO-implicit-declaration.patch BuildRequires: autoconf @@ -32,24 +32,18 @@ BuildRequires: pkgconfig BuildRequires: pkgconfig(libsoc) BuildRequires: pkgconfig(python3) -# Usefull only on arm but x86_64 is faster for building/testing +# Useful only on ARM, but x86_64 is faster for building/testing ExclusiveArch: aarch64 x86_64 %description -This is the rudimentary beginnings of the 96BoardGPIO library to control -real world hardware via the GPIO on the 96Boards family of boards that -confirm to the CE spec. - -One of the cool things about the 96Boards CE project is that all of the -boards use the same pins for the Low Speed Expansion Connector so you can -plug any expansion board into any 96Board and it will connect electrically -BUT there is an issue where GPIO is concerned. Different SoC's have -different GPIO pins. So even though electrically the pins are in the same -place it takes different code to enable and use the GPIO on pins 23 - 34. -Not so fun. +This is 96BoardGPIO library, which controls hardware via the GPIO on +the 96Boards family of boards that confirm to the CE spec. These +boards have the same Low Speed Expansion Connector, but different +SOCs have different GPIO pins for which different code needs to be +used to enable pins 23-34 on the connector. -The 96BoardGPIO library tries to abstract the info so that you can just -tell it what board you are using and what pins you want to use and the +The 96BoardGPIO library abstracts the info so that it can be told +what board is being used and what pins are to be used, and the library does the rest. %package -n lib%{name}%{sover} @@ -58,20 +52,18 @@ Recommends: %{name}-common %description -n lib%{name}%{sover} -This is the rudimentary beginnings of the 96BoardGPIO library to control -real world hardware via the GPIO on the 96Boards family of boards that -confirm to the CE spec. - -One of the cool things about the 96Boards CE project is that all of the -boards use the same pins for the Low Speed Expansion Connector so you can -plug any expansion board into any 96Board and it will connect electrically -BUT there is an issue where GPIO is concerned. Different SoC's have -different GPIO pins. So even though electrically the pins are in the same -place it takes different code to enable and use the GPIO on pins 23 - 34. -Not so fun. +This is 96BoardGPIO library, which controls hardware via the GPIO on +the 96Boards family of boards that confirm to the CE spec. -The 96BoardGPIO library tries to abstract the info so that you can just -tell it what board you are using and what pins you want to use and the +All such boards use the same pins for the Low Speed Expansion +Connector, so any expansion board can be plugged into any 96Board, +and it will connect electrically. However, different SoCs have +different GPIO pins. Even though, electrically, the pins are in the +same place, it takes different code to enable and use the GPIO on +pins 23-34. + +The 96BoardGPIO library abstracts the info so that it can be told +what board is being used and what pins are to be used, and the library does the rest. This package contains shared library for %{name}. @@ -81,20 +73,14 @@ Group: Development/Languages/C and C++ %description -n %{name}-common -This is the rudimentary beginnings of the 96BoardGPIO library to control -real world hardware via the GPIO on the 96Boards family of boards that -confirm to the CE spec. - -One of the cool things about the 96Boards CE project is that all of the -boards use the same pins for the Low Speed Expansion Connector so you can -plug any expansion board into any 96Board and it will connect electrically -BUT there is an issue where GPIO is concerned. Different SoC's have -different GPIO pins. So even though electrically the pins are in the same -place it takes different code to enable and use the GPIO on pins 23 - 34. -Not so fun. +This is 96BoardGPIO library, which controls hardware via the GPIO on +the 96Boards family of boards that confirm to the CE spec. These +boards have the same Low Speed Expansion Connector, but different +SOCs have different GPIO pins for which different code needs to be +used to enable pins 23-34 on the connector. -The 96BoardGPIO library tries to abstract the info so that you can just -tell it what board you are using and what pins you want to use and the +The 96BoardGPIO library abstracts the info so that it can be told +what board is being used and what pins are to be used, and the library does the rest. This package contains common config files for %{name}. @@ -105,20 +91,14 @@ Requires: lib%{name}%{sover} = %{version} %description -n python3-%{name} -This is the rudimentary beginnings of the 96BoardGPIO library to control -real world hardware via the GPIO on the 96Boards family of boards that -confirm to the CE spec. - -One of the cool things about the 96Boards CE project is that all of the -boards use the same pins for the Low Speed Expansion Connector so you can -plug any expansion board into any 96Board and it will connect electrically -BUT there is an issue where GPIO is concerned. Different SoC's have -different GPIO pins. So even though electrically the pins are in the same -place it takes different code to enable and use the GPIO on pins 23 - 34. -Not so fun. +This is 96BoardGPIO library, which controls hardware via the GPIO on +the 96Boards family of boards that confirm to the CE spec. These +boards have the same Low Speed Expansion Connector, but different +SOCs have different GPIO pins for which different code needs to be +used to enable pins 23-34 on the connector. -The 96BoardGPIO library tries to abstract the info so that you can just -tell it what board you are using and what pins you want to use and the +The 96BoardGPIO library abstracts the info so that it can be told +what board is being used and what pins are to be used, and the library does the rest. This package contains python bindings for %{name}. @@ -129,20 +109,14 @@ Requires: lib%{name}%{sover} = %{version} %description devel -This is the rudimentary beginnings of the 96BoardGPIO library to control -real world hardware via the GPIO on the 96Boards family of boards that -confirm to the CE spec. - -One of the cool things about the 96Boards CE project is that all of the -boards use the same pins for the Low Speed Expansion Connector so you can -plug any expansion board into any 96Board and it will connect electrically -BUT there is an issue where GPIO is concerned. Different SoC's have -different GPIO pins. So even though electrically the pins are in the same -place it takes different code to enable and use the GPIO on pins 23 - 34. -Not so fun. +This is 96BoardGPIO library, which controls hardware via the GPIO on +the 96Boards family of boards that confirm to the CE spec. These +boards have the same Low Speed Expansion Connector, but different +SOCs have different GPIO pins for which different code needs to be +used to enable pins 23-34 on the connector. -The 96BoardGPIO library tries to abstract the info so that you can just -tell it what board you are using and what pins you want to use and the +The 96BoardGPIO library abstracts the info so that it can be told +what board is being used and what pins are to be used, and the library does the rest. This package contains development files for %{name}.
