[ANN] compat32pkg-1.3.110319 is out !
 

Hello Slackers,

I come today with a new version of compat32pkg, which corrects the design flaw pointed out by tobyl here, includes a new feature,
and, the latest revision of the configuration file for the "layer-32", which comes with the latest changes made by Eric Hameleers
to the "32-bit part of the multilib".

You can grab this new revision at compat32pkg's website or using this direct link.


So, compat32pkg had a design flaw ?

Yes, that's right !

In fact, the update mechanism was designed to search updates for installed packages only, which, in the case of the "layer-32", was
an error. This was corrected in this new revision, and, now, the update mechanism for the "layer-32", recognizes as an update :
(1) any new version of any installed package of the "32-bit part of the multilib", and, (2) any package of the "32-bit part of the multilib"
which is not installed, nor blacklisted, nor excluded. This implies that any addition (of package) into the configuration file for the "layer-32"
is handled as an update.

So, if we try this new compat32pkg, in mode --list-updates for example, on a slackware whose the "layer-32" is not fully installed, it will report
the found updates which includes a certain amount of new packages, like below:

This new version of compat32pkg comes also with the new feature --layer 32-config, which allows, when needed, updating of configuration file for the "layer-32"
to the latest revision available on an updates-site dedicated to compat32pkg.

This was designed so that users can take advantage of any changes made to the "layer-32" as quickly and as easily as possible.

For example, to test whether the installed configuration file for the "layer-32" is up to date, compat32pkg will have to be used this way :

Here is an example of the output of this feature when an update is available :


When an update is available, compat32pkg will have to be used as below to upgrade the installed configuration file for "layer-32" to the latest revision :

Here is an example of updating the configuration file for "layer-32" :

Hoping this release will be as useful as possible ...

Cheers !

--
SeB

Thanks!:hattip:

For those upgrading, don't forget to check those *.new config files, like I did. :doh:

SeB,

Nice work!
I have not tested to destruction, but as far as I can tell, the new version works flawlessly.
I used compat32pkg to install the recent updates, and also removed a package to see if compat32pkg could inform me of the missing package, and it was successful.
I didn't prove the config update because I had already updated.

chrisretusn: when using slackpkg, you are automatically reminded of .new files, keeping current on -current has never been easier.

tobyl

Yes but, upgrading compat32pkg package does not involve running slackpkg. :)

Yes I know I can run "slackpkg new-config" after running "upgradepkg compat32pkg".

In my excitement to test out the new compat32pkg I simply forgot to merge the changes to the configuration files and first (listing) run of comat32pkg did not show as expected. That is the reason for the :doh: moment.

Hello,

:D Pleased to see that all is doing well !


You can (safely) test this by doing one of the following:

• remove (or rename) /etc/compat32pkg/multilib-32bit-packages.lst
  
• remove the version information (ie given in first line) into /etc/compat32pkg/multilib-32bit-packages.lst
  
• change the version information into /etc/compat32pkg/multilib-32bit-packages.lst. If you set this version to an older one (ie < 1.3.110319),
  the update mechanism should tell you that an update is available, otherwise it should not.

I made the update mechanism for this file as simple as possible. On the "updates-site" there must be two files. (1) the latest revision of
multilib-32bit-packages.lst, and (2) an information file called multilib-32bit-packages.lst.infos which must contains the following data :

1. The version number of the "new" multilib-32bit-packages.lst given into a field named "version" as below :
   
   Code:

   ---

           version = 1.3.110601

   ---

2. The md5sum of the "new" multilib-32bit-packages.lst given into a field named "version" as below :
   
   Code:

   ---

           md5sum = 6f7d19e164201754d28a66c59913afed

   ---

3. The description of changes since the previous revision, given into lines starting by a character ":", as below :
   
   Code:

   ---

             :This is the description of changes since the previous revision of the file
          :that describes the layer-32.
          :  + package X was added. This does not affect the multilib for 13.0

   ---

The default "updates-site" is at http://sourceforge.net/projects/comp...s/updates-site. The "alternate updates-site" at
http://compat32pkg.sourceforge.net/updates-site (clicking on this will give you a 403 error) can be passed in argument
of layer-32-config as below:


Well, I wanted to add something into the "doinst.sh" to prevent that kind of problem, but, I changed my mind
at the last time because I thought I was the only one to forgot to check this. :p


Cheers !
--
SeB

I'm willing to bet we are not alone. ;)

Hello,

An update is available for the file that describes the layer-32. Users of 1.3.110319 can check-update/update
for this one as below :

P.S:there's a tiny bug into the code that extract informations about latest update. So you're going to see
some truncated lines into the description of changes made since the latest revision. I will publish a new
revision of compat32pkg (1.3.110319 build 4) tomorrow.

P.S: Well, the 1.3.110319 build 4 is now online.

--
SeB