hardware_information 1.0.83

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 4087e89cb73b455fcab014e76b247cdd625a1139ca482529713dd4f83aaa02f4
+  data.tar.gz: b9a2905adf53d06674e532ef2b448107863789ef6ab6ff619e389a9edb86a362
+SHA512:
+  metadata.gz: ee8927ef80715d22e2c98838e84764b87b812a33a2c01a546a9f9fc975f30a7090f81217e01149b16ed737b08fe68b83aa9ad06fce131f3cba901f2ba40d1e82
+  data.tar.gz: 112500cefbe7e4a8f85c71a506c4812502ab8928b460ca0cf4c026727d6fcf75757ee9acea7c98411cdedbcbf7b4c5cc76fd5c269482b22809c97654d77412d6

data/README.md

@@ -0,0 +1,94 @@
+[![forthebadge](https://forthebadge.com/images/badges/built-with-love.svg)](https://www.gobolinux.org/)
+[![forthebadge](https://forthebadge.com/images/badges/made-with-ruby.svg)](https://www.ruby-lang.org/en/)
+[![Gem Version](https://badge.fury.io/rb/hardware_information.svg)](https://badge.fury.io/rb/hardware_information)
+
+This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">06.06.2023</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">13:01:37</span> o'clock.
+
+# The HardwareInformation Project
+
+<img src="https://i.imgur.com/v7paEUT.png" style="margin: 1em; border: 4px solid black;">
+
+The above image has been partially auto-generated by cfdg 
+(context free design grammar). The cfdg gallery can be
+seen at: https://www.contextfreeart.org/gallery/search.php?t=new&num=25
+
+You can re-use the above image and change / re-shape it in any way,
+shape or form, under a <b>CC BY-SA 4.0</b>, if you would like to.
+(I should improve the image and remove the edgy blur effects,
+but it is just some logo so that this gem also has a logo. I
+did not want to invest too much time into this logo.)
+
+The CC BY-SA licence can be read here: https://creativecommons.org/licenses/by-sa/4.0/
+
+## Requiring the HardwareInformation gem
+
+You can require this gem via:
+
+    require 'hardware_information'
+
+## HardwareInformation.report
+
+This toplevel API will report what hardware has been found
+on the given computer system.
+
+## Colour support
+
+By default class HardwareInformation will try to show colours,
+if used from the commandline.
+
+If this is unwanted, you can pass any of the following flags
+to disable colour support:
+
+    --disable-colours
+    --disable-colors
+    --no-colours
+    --no-colors
+
+## Example screenshot of the output generated by class Hardwareinformation
+
+<img src="https://i.imgur.com/cIqwg5V.png" style="margin: 1em">
+
+
+## Contact information and mandatory 2FA coming up in 2022
+
+If your creative mind has ideas and specific suggestions to make this gem
+more useful in general, feel free to drop me an email at any time, via:
+
+    shevy@inbox.lt
+
+Before that email I used an email account at Google gmail, but in **2021** I
+decided to slowly abandon gmail, for various reasons. In order to limit the
+explanation here, allow me to just briefly state that I do not feel as if I
+want to promote any Google service anymore when the user becomes the 
+product (such as via data collection by upstream services). I feel this is
+a hugely flawed business model.
+
+Do keep in mind that responding to emails may take some time, depending on
+the amount of work I may have at that moment.
+
+In <b>2022</b> rubygems.org, or rather the corporate overlords who control the
+rubygems.org infrastructure these days, decided to make 2FA mandatory for every
+gem owner eventually: see
+https://blog.rubygems.org/2022/06/13/making-packages-more-secure.html
+
+Mandatory 2FA will eventually be extended to all rubygems.org developers and
+maintainers. As I can not use 2FA, for reasons I will skip explaining here,
+this means that my projects will eventually be taken over by shopify (or,
+correspondingly, whoever effectively controls the rubygems.org ecosystem).
+At that point, I no longer have any control what is done to my projects
+since shopify (respectively those controlling the gems ecosystem) took away
+control here. Not sure at which point ruby became corporate-controlled -
+that was not the case several years ago.
+
+Ruby also only allows 2FA users to participate on the issue tracker these
+days:
+
+  https://bugs.ruby-lang.org/issues/18800
+
+(Note that this was changed a few months ago, so the last part is no
+longer valid - it is possible to register again without mandating 
+2FA. I will retain the above notice for a bit longer, though, as I feel
+we should not restrict communication via mandatory authentification
+in general. Fighting spam is a noble goal, but when it also means you
+lock out real human people then this is definitely NOT good.)
+

data/bin/hardware_information

@@ -0,0 +1,12 @@
+#!/usr/bin/ruby -w
+# Encoding: UTF-8
+# frozen_string_literal: true
+# =========================================================================== #
+require 'hardware_information'
+
+_ = HardwareInformation.new(:do_not_run_yet)
+unless ARGV.empty?
+  _.menu(ARGV)
+end
+_.run
+_.report_result

data/doc/README.gen

@@ -0,0 +1,47 @@
+DEFAULT_HEADER
+
+# The HardwareInformation Project
+
+<img src="https://i.imgur.com/v7paEUT.png" style="margin: 1em; border: 4px solid black;">
+
+The above image has been partially auto-generated by cfdg 
+(context free design grammar). The cfdg gallery can be
+seen at: https://www.contextfreeart.org/gallery/search.php?t=new&num=25
+
+You can re-use the above image and change / re-shape it in any way,
+shape or form, under a <b>CC BY-SA 4.0</b>, if you would like to.
+(I should improve the image and remove the edgy blur effects,
+but it is just some logo so that this gem also has a logo. I
+did not want to invest too much time into this logo.)
+
+The CC BY-SA licence can be read here: https://creativecommons.org/licenses/by-sa/4.0/
+
+## Requiring the HardwareInformation gem
+
+You can require this gem via:
+
+    require 'hardware_information'
+
+## HardwareInformation.report
+
+This toplevel API will report what hardware has been found
+on the given computer system.
+
+## Colour support
+
+By default class HardwareInformation will try to show colours,
+if used from the commandline.
+
+If this is unwanted, you can pass any of the following flags
+to disable colour support:
+
+    --disable-colours
+    --disable-colors
+    --no-colours
+    --no-colors
+
+## Example screenshot of the output generated by class Hardwareinformation
+
+<img src="https://i.imgur.com/cIqwg5V.png" style="margin: 1em">
+
+ADD_CONTACT_INFORMATION

data/hardware_information.gemspec

@@ -0,0 +1,38 @@
+# =========================================================================== #
+# Gemspec for Project HardwareInformation.
+# =========================================================================== #
+require 'hardware_information/version/version.rb'
+require 'roebe/toplevel_methods/misc.rb'
+
+Gem::Specification.new { |s|
+
+  s.name    = 'hardware_information'
+  s.version = HardwareInformation::VERSION
+  s.date    = Time.now.strftime('%Y-%m-%d')
+  
+  DESCRIPTION = <<-EOF
+
+This small class will output Information about your hardware,
+i.e. the Processor type and so on. This presently only works
+on Linux, though.
+
+  EOF
+  s.summary     = DESCRIPTION
+  s.description = DESCRIPTION
+
+  s.authors  = ['Robert A. Heiler']
+  s.email    = Roebe.email?
+  s.files    = Dir['**/*']
+  s.homepage = 'https://rubygems.org/gems/environment_information'
+  s.license  = 'GPL-2.0'
+
+  s.required_ruby_version     = '>= '+Roebe.third_most_stable_version_of_ruby
+  s.required_rubygems_version = '>= '+Gem::VERSION
+  s.rubygems_version          = '>= '+Gem::VERSION
+
+  # ============================================================== #
+  # Dependencies
+  # ============================================================== #
+  s.add_dependency 'colours'
+
+}