repackage 1.2.1 → 1.2.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: cce85a8c9a73901eba853de68bcc06899e501d1ea49ef9d331f884d82fd309d4
-  data.tar.gz: d8849e6c2f2670d4eb5fa8516ca013d3ffba3fc3923e42759fb500f818e59176
+  metadata.gz: 6d610e7f324e47b9e501b722ce8bf28550742789e468d1185498b71ea477b269
+  data.tar.gz: 18b077a70111c97f9a5b3483083bfd8f742cb0502a7c349f64d97fb9ce3322a1
 SHA512:
-  metadata.gz: 1d13d34ebbed709e1187228512e2af63adf524a28dbcf08e51a0d65763d7f5df6b43875b48a78363b2fc0e90c81a73ae0c557861f982cc9b6de6583ef04173c0
-  data.tar.gz: 49150a9e9efbd1f2b1c51db8302acc85d737b7bffb5a9c39fa844cfb9bfd17b0caab57cbe4e2e9846ad2103151ffcebde9f91fbc3733d459a49b03872198eb61
+  metadata.gz: c9381c5789becfaebbfd8d6b27b1d8261e29cbb73aea3ccbf3fe63d427a42c38de120003c42a3679f96e7a5434fe71862f951a959a7c72d94b4db3764b9e52b0
+  data.tar.gz: 2847b21d2719e21d2b89842b23b252ab12238f445f06b12bc61e96aceaef843b893c06e0ad6f8ad8e93c6d057bf60ce5d49763eee46dc4dd8aa5ee283d478f21

data/README.md

@@ -2,7 +2,7 @@
 [![forthebadge](https://forthebadge.com/images/badges/made-with-ruby.svg)](https://www.ruby-lang.org/en/)
 [![Gem Version](https://badge.fury.io/rb/repackage.svg)](https://badge.fury.io/rb/repackage)
 
-This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">12.09.2022</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">04:23:04</span> o'clock.
+This gem was <b>last updated</b> on the <span style="color: darkblue; font-weight: bold">11.11.2023</span> (dd.mm.yyyy notation), at <span style="color: steelblue; font-weight: bold">04:41:00</span> o'clock.
 
 # The repackage gem
 
@@ -23,6 +23,12 @@ The official list of dependencies thus recommended for the
 - extracter
 - opn
 
+However had, since as of November 2023, the colours gem is now
+optional. If it is installed on your system then it will be
+used; otherwise it will be silently ignored. Colours are nice
+to have, but the repackage gem must also work with colours
+not being available (e. g. the colours gem was NOT installed).
+
 ## Clean working directory
 
 As far as the **repackage** gem is concerned, a working
@@ -68,12 +74,13 @@ flexibility here.
 
 ## Executable at bin/repackage
 
-Since as of May 2022 there is now an executable called
-<b>repackage</b>. It used to be called repackager,
-but I reconsidered; it seems simpler to remember
-that the gem called <b>repackage</b> comes with an
-executable called <b>repackage</b> rather than
-<b>repackager</b>.
+Since as of May 2022 there is now an <b>executable</b> called
+<b>repackage</b>. It used to be called <b>repackager</b>,
+but I reconsidered; it seems simpler to remember that the gem
+here is called <b>repackage</b>; then people may easily 
+and instantly know that there may be an executable called
+<b>repackage</b>, residing at bin/repackage, rather than
+a file residing at <b>bin/repackager</b>.
 
 
 ## Contact information and mandatory 2FA coming up in 2022
@@ -84,35 +91,53 @@ 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 this
+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, for various reasons.
-
-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 2022 rubygems.org decided to make 2FA mandatory for every gem owner:
-see https://blog.rubygems.org/2022/06/13/making-packages-more-secure.html
-
-As I can not use 2FA, for reasons I will skip explaining here (see
-various github issue discussions in the past), this effectively means that
-Betty Li and others who run the show at rubygems.org will perma-ban me
-from using rubygems as a developer.
-
-As I disagree with that decision completely, this will mean that all my
-gems will be removed from rubygems.org prior to that sunset date, e. g.
-before they permanently lock me out from the code that I used
-to maintain. It is pointless to want to discuss this with them anymore -
-they have made up their minds and decided that you can only use
-the code if 2FA is in place, even though the code itself works just
-fine. If you don't use 2FA you are effectively locked out from your
-own code; I consider this a malicious attack. See also how they limited
-discussions to people with mandatory 2FA on the ruby-bugtracker, thus
-banning everyone permanently without 2FA:  
-
-https://bugs.ruby-lang.org/issues/18800
-
-Guess it may indeed be time to finally abandon ruby - not because
-ruby is a bad language, but there are people now in charge who
-really should not be part of ruby in the first place.
+want to promote any Google service anymore when the user becomes the end
+product (such as via data collection by upstream services, including other
+proxy-services). My feeling is that this is a hugely flawed business model
+to begin with, and I no longer wish to support this in any way, even if
+only indirectly so, such as by using services of companies that try to
+promote this flawed model.
+
+In regards to responding to emails: please keep in mind that responding 
+may take some time, depending on the amount of work I may have at that
+moment. So it is not that emails are ignored; it is more that I have not
+(yet) found the time to read and reply. This means there may be a delay
+of days, weeks and in some instances also months. There is, unfortunately,
+not much I can do when I need to prioritise my time investment, but I try
+to consider <b>all</b> feedback as an opportunity to improve my projects
+nonetheless.
+
+In <b>2022</b> rubygems.org 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 removed, as I no longer
+have any control over my projects hosted on rubygems.org (because I
+can not use 2FA).
+
+At that point, I no longer have any control what is done to my projects
+since whoever is controlling the gems ecosystem took away our control
+here. I am not sure at which point ruby became corporate-controlled -
+that was not the case several years ago, so something has
+changed.
+
+Ruby also only allows 2FA users to participate on the issue tracker these
+days:
+
+  https://bugs.ruby-lang.org/issues/18800
+
+But this has been reverted some months ago, so it is no longer applicable.
+Suffice to say that I do not think that we should only be allowed to
+interact on the world wide web when some 'authority' authenticated us,
+such as via mandatory 2FA, so I hope this won't come back again.
+
+Fighting spam is a noble goal, but when it also means you lock out
+real human people then this is definitely NOT a good situation
+to be had.
 

data/lib/repackage/class/misc.rb

@@ -49,13 +49,6 @@ class Repackage # === Repackage::Repackage
     i.squeeze '/'
   end
 
-  # ========================================================================= #
-  # === cliner
-  # ========================================================================= #
-  def cliner
-    e rev+('=' * 80)
-  end
-
   # ========================================================================= #
   # === try_glob
   #
@@ -295,13 +288,6 @@ class Repackage # === Repackage::Repackage
     )
   end
 
-  # ========================================================================= #
-  # === rev
-  # ========================================================================= #
-  def rev
-    ::Repackage.rev
-  end
-
   # ========================================================================= #
   # === extract_to_this_directory?
   # ========================================================================= #
@@ -704,23 +690,6 @@ class Repackage # === Repackage::Repackage
     end
   end
 
-  # ========================================================================= #
-  # === remove_the_old_archive
-  #
-  # Only call this when we are sure to remove the old source. I recommend
-  # to delete the old source. Of course we must make sure to delete the
-  # right package.
-  # ========================================================================= #
-  def remove_the_old_archive(
-      i = dir_where_the_archive_resides?+filename?
-    )
-    opn; e "Removing the old archive at #{sfile(i)}"
-    opn; e "next, as requested via the "\
-           "#{::Repackage.steelblue('SHALL_WE_DELETE_THE_OLD_ARCHIVE')} "\
-           "constant."
-    remove(i)
-  end
-
   # ========================================================================= #
   # === extract                                                 (extract tag)
   #
@@ -768,16 +737,18 @@ class Repackage # === Repackage::Repackage
         # format.
         # =================================================================== #
         if is_it_already_in_the_correct_archive_format?(this_file)
-          opn; e rev+'The file at '+sfile(this_file)+' is already in '\
-                 'the desired target format ('+target_format?+').'
-          opn; e "Repackaging into the same target format makes no sense, "\
+          opn; e rev+'The file at '+sfile(this_file)+rev+' is already in '\
+                 'the desired target format ('+target_format?+
+                 rev+').'
+          opn; e "#{rev}Repackaging into the same target format makes no sense, "\
                  "thus aborting now."
         else
-          opn; e 'We will try to repackage this archive into the `'+
-                  simp(target_format_type?)+'`'
-          opn; e 'format type.'
-          opn; e 'It will be extracted into the directory '+
-                  sdir(extract_to?)+'.'
+          opn; e rev+'We will try to repackage this archive into the `'+
+                  simp(target_format_type?)+rev+'`'
+          opn; e rev+'format type.'
+          opn; e rev+'It will be extracted into the directory '+
+                 sdir(extract_to?)+
+                 rev+'.'
           # ================================================================= #
           # Here we know that the file exists and that it can be repackaged
           # into another target format. Thus, we can repackage it. We
@@ -839,17 +810,19 @@ class Repackage # === Repackage::Repackage
   # === repackage_this_particular_file
   # ========================================================================= #
   def repackage_this_particular_file(this_file)
-    opn; e rev+'The file '+sfile(this_file)+' will be repackaged '\
-           'into the '+orange(repackage_to_which_format?)+' format.'
+    opn; e rev+'The file '+sfile(this_file)+rev+' will be repackaged '\
+           'into the '+rev+
+           orange(repackage_to_which_format?)+
+           rev+' format.'
     copy_this_file_to_the_working_directory(this_file)
     working_directory = working_directory?
     cd(working_directory) # Go to the working directory.
     set_start_dir(working_directory)
-    opn; e 'Working from the directory `'+sdir(working_directory)+'` next.'
+    opn; e rev+'Working from the directory `'+sdir(working_directory)+
+           rev+'` next.'
     absolute_path = File.absolute_path(this_file)
-    opn; e 'The actual file that will be used for the '\
-           'repackaging'
-    opn; e 'step now resides at: '
+    opn; e rev+'The actual file that will be used for the repackaging'
+    opn; e rev+'step now resides at: '
     e
     e "  #{sdir(absolute_path)}"
     e
@@ -922,6 +895,37 @@ class Repackage # === Repackage::Repackage
     @internal_hash[:extract_to_this_directory] = i
   end; alias set_extract_to_this_directory set_extract_to # === set_extract_to_this_directory
 
+  # ========================================================================= #
+  # === cliner
+  # ========================================================================= #
+  def cliner
+    e rev+('=' * 80)
+  end
+
+  # ========================================================================= #
+  # === rev
+  # ========================================================================= #
+  def rev
+    ::Repackage.rev
+  end
+
+  # ========================================================================= #
+  # === remove_the_old_archive
+  #
+  # Only call this when we are sure to remove the old source. I recommend
+  # to delete the old source. Of course we must make sure to delete the
+  # right package.
+  # ========================================================================= #
+  def remove_the_old_archive(
+      i = dir_where_the_archive_resides?+filename?
+    )
+    opn; e "Removing the old archive at #{sfile(i)}"
+    opn; e "next, as requested via the "\
+           "#{::Repackage.steelblue('SHALL_WE_DELETE_THE_OLD_ARCHIVE')} "\
+           "#{rev}constant."
+    remove(i)
+  end
+
   # ========================================================================= #
   # === run                                                         (run tag)
   # ========================================================================= #

data/lib/repackage/version/version.rb

@@ -9,11 +9,11 @@ module Repackage
   # =========================================================================== #
   # === VERSION
   # =========================================================================== #
-  VERSION = '1.2.1'
+  VERSION = '1.2.3'
 
   # =========================================================================== #
   # === LAST_UPDATE
   # =========================================================================== #
-  LAST_UPDATE = '06.11.2023'
+  LAST_UPDATE = '11.11.2023'
 
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: repackage
 version: !ruby/object:Gem::Version
-  version: 1.2.1
+  version: 1.2.3
 platform: ruby
 authors:
 - Robert A. Heiler
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-11-06 00:00:00.000000000 Z
+date: 2023-11-11 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: extracter