Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. New innreport-display.conf file (Julien ?LIE)
   2. About external or technical configuration files (Julien ?LIE)


----------------------------------------------------------------------

Message: 1
Date: Sat, 16 Apr 2022 12:20:13 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: New innreport-display.conf file
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi all,

Following a previous discussion, I've just separated innreport.conf into 2 
files.
Special care is needed to handle that change if you made local modifications to 
the display.  This is mentioned in the upgrade instructions for INN 2.7:

     * The innreport.conf file in pathetc has been split into a general
       configuration file (innreport.conf itself) and a display configuration
       file (innreport-display.conf in *pathlib*).  If you made local changes
       in sections other than the *default* section in innreport.conf, and
       wish to keep them, then you need renaming the new
       innreport-display.conf file to a another name in *pathlib*, setting
       this local file name in the new *display_conf_file* option in
       innreport.conf, and re-applying your local changes to that local
       display configuration file.

       As a matter of fact, the default display configuration file would
       otherwise be overwritten each time INN is updated.  Bug fixes or
       enhancements are made from time to time to the display configuration
       of innreport, and couldn't be automatically be merged in
       innreport.conf on update.  This new separate configuration file to
       parameter the display will now permit an automatic update (if of
       course you use the default display configuration file).



This is one of the latest "disruptive" change for the end user I've had in mind 
for INN 2.7.0 (switching to Automake can be handled transparently for the end 
user in a minor release in the 2.7.x series).


Does anyone here have any other wish for INN 2.7.0 that need special upgrade 
instructions?

-- 
Julien ?LIE

??Tant qu'il y a des marmites, il y a de l'espoir?!?? (Ast?rix)


------------------------------

Message: 2
Date: Sat, 16 Apr 2022 12:41:10 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: About external or technical configuration files
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed

Hi all,

Do you think something should be done for the following configuration 
files in <pathetc>, that are not automatically updated with a new INN 
version?
- control.ctl
- innwatch.ctl
- moderators
- nocem.ctl

Currently, a news admin needs taking care manually of possible changes.

I doubt people really modify innwatch.ctl...  It may be a file to move 
into <pathlib> so that bug fixes are automatically taken into account 
during an update.
We could have the following behaviour:  use <pathetc>/innwatch.ctl.local 
if present.  Otherwise, use <pathlib>/innwatch.ctl.
Any opinion about that?


Changes to control.ctl and nocem.ctl are not always straight-forward, as 
a manual intervention in PGP keys could be needed.  So I would be 
inclined not to change anything, unless someone has an interesting idea.

Besides, changes to these "external" files can happen at any time, and 
are not linked to an INN release.  Same thing for the moderators file.

Maybe a simple tool that the admin could manually start, or put in cron, 
that just download the reference file (from ftp.isc.org or the GitHub 
INN repository for instance) and output the diff between the local 
installed file could be useful and be an improvement?

Incidentally, this tool may also download/compare the installed version 
of other common packages like Cleanfeed, PyClean or like.

-- 
Julien ?LIE

??Lots of people want to ride with you in the limo, but what you want is
   someone who will take the bus with you when the limo breaks down.??
   (Oprah Winfrey)


------------------------------

Subject: Digest Footer

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers


------------------------------

End of inn-workers Digest, Vol 140, Issue 2
*******************************************

Reply via email to