I can test on both SME8 & SME9
excellent!
I can manipulate existing templates, not sure about creating new ones from scratch, possibly with guidance.
here is a reference :
https://wiki.contribs.org/Template_Tutorialwell this is the simplest part.
first step is to take an example conf file from the original dansguardian rpm.
then you try to cut the content in different files, with file name startint with numbers to order them,
This is an example of breakdown:
10intro
20generalconf
30lists
40exclusions
50antivirus
55alternateantivirus
80other
At this step there is only two things you must pay attention : { and }. They have to be escaped or what is inside will be interpreted by perl : \{ and \}
Having fragment instead of a whole file will help final user to only override a part of the template (ie 50antivirus), and will help to maintain the package with upstream updates.
You place all theses files in a folder.
/etc/e-smith/templates/etc/dansguardian/dansguardian.conf
you now have a static template with multiple fragments, congratulation !
Second step is to add some perl magic. This is where you use some {} and call the db values to fill the content. You can get example from the other contribs or from the existing contrib in the smedev repo.
I can give a hand there.
Third step is to fill the default db, create migrate fragments, this is more tricky and
I can handle this part.
Fourth step is to update the panel to be able to access all our new configurations. This is also a tricky part
I can handle.
Finally we package all the modifications with patches or with a new archive and we build a new rpm with the buildsystem ! Again in this part
I can handle this, unless you start feeling the developer in you !
Optionally some translation might occurs in pootle... and we add them to the rpm.
of course we need to test at every step, and can do intermediate builds between steps.
16 Replies
5111 Views