aboutsummaryrefslogtreecommitdiffstats
path: root/inxi.changelog
diff options
context:
space:
mode:
authorLibravatarUnit 193 <unit193@ubuntu.com>2015-08-17 15:48:31 -0400
committerLibravatarUnit 193 <unit193@ubuntu.com>2015-08-17 15:48:31 -0400
commit35ddf848228bfd4748f84d58a1d741d0623d2b66 (patch)
treedd3718445caad5bfc3c438d7018cd09887f42bd4 /inxi.changelog
parentb8f908878d9f473ee3b030228ba1487c6de02f9d (diff)
downloadinxi-35ddf848228bfd4748f84d58a1d741d0623d2b66.tar.bz2
inxi-35ddf848228bfd4748f84d58a1d741d0623d2b66.tar.xz
inxi-35ddf848228bfd4748f84d58a1d741d0623d2b66.tar.zst
Imported Upstream version 2.2.27upstream/2.2.27
Diffstat (limited to 'inxi.changelog')
-rwxr-xr-xinxi.changelog164
1 files changed, 164 insertions, 0 deletions
diff --git a/inxi.changelog b/inxi.changelog
index 2242ad5..5144feb 100755
--- a/inxi.changelog
+++ b/inxi.changelog
@@ -1,4 +1,168 @@
=====================================================================================
+Version: 2.2.27
+Patch Version: 00
+Script Date: 2015-08-02
+-----------------------------------
+Changes:
+-----------------------------------
+New version, tarball. Trivial wget/curl change, nothing else. No need to upgrade packages.
+
+-----------------------------------
+-- Harald Hope - Sun, 02 Aug 2015 14:18:45 -0700
+
+=====================================================================================
+Version: 2.2.26
+Patch Version: 00
+Script Date: 2015-07-06
+-----------------------------------
+Changes:
+-----------------------------------
+New version, new tarball. This fixes a bug with the last fix for KDE Plasma version. It was
+showing Frameworks version, which is apparently NOT the same as the plasma version.
+
+Also added debugger kde versioning to make this stuff less of an ordeal for data collection.
+
+-----------------------------------
+-- Harald Hope - Mon, 06 Jul 2015 15:51:51 -0700
+
+
+=====================================================================================
+Version: 2.2.25
+Patch Version: 00
+Script Date: 2015-06-15
+-----------------------------------
+Changes:
+-----------------------------------
+Same version, new tarball, I'm tossing this in with the other release, changing for kde >= 4,
+changing simple KDE to KDE Plasma, which keeps it clear and simple.
+
+-----------------------------------
+-- Harald Hope - Mon, 15 Jun 2015 18:00:42 -0700
+
+=====================================================================================
+Version: 2.2.25
+Patch Version: 00
+Script Date: 2015-06-15
+-----------------------------------
+Changes:
+-----------------------------------
+New version, new tarball. Got a good fix for the kde version issue from the lads at
+#kde-devel, now using kf5-config --version which gives similar output to kded4 --version
+
+I use this for both 4 and 5, but since 4 has worked fine for years, I'll just use this for 5
+and later.
+
+-----------------------------------
+-- Harald Hope - Mon, 15 Jun 2015 17:49:56 -0700
+
+=====================================================================================
+Version: 2.2.24
+Patch Version: 00
+Script Date: 2015-06-15
+-----------------------------------
+Changes:
+-----------------------------------
+new version, new tarball. Adapted to deal with yet another silly pointless change from
+normal, in this case, sddm decided that using a .pid or .lock file in /run was too easy
+so they changed to some session id type string in the /run/sddm/ directory.
+
+Speaking for myself, I find such pointless changes from anything resembling normal behaviors
+to the reason that gnu freedesktop systems will never achieve significant desktop use globally.
+
+Also, in the same vein, added debuggers to try to figure out what plasma5/kde 5 is using
+internally to give command line version information. Again, something pointless internally
+was changed, thus breaking something that had faintly resembled an api, which is of course
+why desktop gnu linux will never actually take off, developers in the real world have no
+interest in chasing after such pointless and never ending churn in even the most trivial
+areas of the OS, let alone the core.
+
+inxi remains however as a log of this ongoing churn and lack of discipline, and so remains
+an interesting process of observation, and a way for users to try to avoid the constant
+changes in simple system queries that should really never change, so I can see a reason
+to keep it going since it's obvious that the actual foss ecosystem itself will not and apparently
+cannot grasp that it is the lack of stable apis, methods, etc, that has kept desktop gnu linux
+from achieving any actual real world success or popularity, and that is the actual problem
+that should be fixed, not some pointless internal change to something.
+
+On the source repo front, maintainers, I still can't find an acceptable alternative to the
+impending shutdown of googlecode. github is a for profit venture that people who seem totally
+void of any sense of history believe is actually going to be around longer than say, sourceforge,
+or googlecode, as a legitimate source hosting site.
+
+I'd welcome any suggestions. So far all the options are bad that I can find.
+
+Top preference is svn, but if git is the absolute only other choice for an otherwise good option,
+I'd consider git, but it's a horrible option for inxi because of how inxi development and debugging
+works, vs how git works. ie, svn branches are perfect, git branches are totally wrong.
+
+I may end up just hosting the svn on my own servers to avoid having to move yet again when the next
+for profit flakey site decides to close up or monetize the source hosting.
+
+The original idea of googlecode was for google to 'pay its dues to the foss community', but apparently
+they got bored with that idea, plus of course, the ongoing total failure of google to deal with
+automated spam, which has always been a huge bug in the core google corporate culture. But googlecode
+was by far the best option I've come across, it was done by a deep pocketed corporation not for profit
+for pretty good reasons, and was never intended to be a profit center, which is the closest I could
+see for a non free option.
+
+Setting up svn gui stuff however is a royal pain and requires ongoing maintainance for the life of
+the software, which is NOT fun, nor will I sign up for that obligation.
+
+I may end up moving to github anyway, even though git truly sucks for inxi and myself, but it's an
+idea I find fairly vile, apparently free software (sic) authors seem to have no grasp of the concept
+of fredom when it comes to source code hosting, judging by the absurd popularity of github as the
+default go to source repo. Their website is pathetic as well, which isn't very promising.
+
+So we'll see where it goes, I think I have until august to decide what to do for source hosting.
+
+Since I'm old enough to have seen sourceforge and now googlecode do the same thing, along with a lot
+of other options, to say github won't do this too is delusional, what you can almost certainly say is it
+will do it, the only question is when. But, just as Linus did with his non free linux kernel version
+control, people will stick with the non free stuff until you realize you can't use it anymore, because
+it is non free. Free software hosted on non free source repos is to me one of the most absurd and
+stupid things I've ever heard of to be honest.
+
+-----------------------------------
+-- Harald Hope - Mon, 15 Jun 2015 15:19:02 -0700
+
+=====================================================================================
+Version: 2.2.23
+Patch Version: 00
+Script Date: 2015-06-08
+-----------------------------------
+Changes:
+-----------------------------------
+New version, tarball. Tiny change. Added /etc/devuan_version file to distro id to handle
+the switched file name. Kudos to anyone out there fighting to create a working alternative
+to the unreliable and buggy and windows emulating systemd, I wish devuan luck. Maybe between
+devuan and gentoo and slackware we can save the free software core systems before it's too late.
+
+-----------------------------------
+-- Harald Hope - Mon, 08 Jun 2015 15:43:52 -0700
+
+=====================================================================================
+Version: 2.2.22
+Patch Version: 00
+Script Date: 2015-05-30
+-----------------------------------
+Changes:
+-----------------------------------
+New version, new man page, new tarball. Modified slightly -tc and -tm output to fix a
+pet peeve of mine. Now, if -I, -b, -F, or anything that can trigger the memory: used/total
+in Information line is not used, -tm will always show the system used/total ram data on the
+first line of the Memory item of -t output.
+
+Also, if -xtc (trigger ram data in cpu output) is used, and -I is not triggered, and -tm is
+not triggered, will also show system used/total ram data on the cpu first line.
+
+I'd found it odd that this data did not appear when -tcm or -tm or -xtc were used, so this is
+now fixed. I used the -t option a fair amount to find memory/cpu use issues, and usually I
+don't use the option with other options, so the lack of total system ram data was odd.
+
+-----------------------------------
+-- Harald Hope - Sat, 30 May 2015 11:50:56 -0700
+
+=====================================================================================
Version: 2.2.21
Patch Version: 00
Script Date: 2015-05-13