Few questions concerning creating addon package

[Robin Roevens <robin.roevens@disroot.org>]

[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]

Hi all

Firstly, thank you Adolf for the encouragement and extra pointers to
start this task.. 
I think I have currently successfully prepared a new version of the
zabbix_agentd package containing latest zabbix_agentd LTS version
(v5.0.9). 

I tested the package on an ipfire-test-vm instance set up with the iso
built by the make.sh script and then manually unpacking the package
using the instructions of
https://wiki.ipfire.org/devel/ipfire-2-x/addon-howto and all seems well
except that the service is not automatically started during install.sh
which calls:
---
restore_backup ${NAME}
start_service --background ${NAME}
---
So I'm assuming ${NAME} is not available when I manually run install.sh
as per instructions, and that it will be available when pakfire itself
installs the package?
Is there a way to test the actual package deployment using pakfire ?

Then I have a few other questions:
- In the LFS template there is a PAK_VER variable, and it is not clear
to me what this exactly is. Is this a revision number for current
packaged version? or just a 'counter' for how many package versions
there have been for this program in IPFire ? 

- In the LFS template for current zabbix_agentd v4.2.6 DL_FROM is
pointing to URL_IPFIRE.. Should this be changed ? Or should I upload
the new source-file for v5.0.9 to URL_IPFIRE in some way ? (are there
instructions somewhere?) or ..?

Then a more practical question:
Next to 'just' an upgrade of the current Zabbix agent I also added a
few config files etc for use with my Zabbix IPFire specific monitoring
template. This changes Alexander's original config a little, but should
remain backwards compatible.
Should I submit this as 2 separate patches or will a single patch
suffice? 

Regards
Robin




-- 
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.