opsi-setup-detector - customizing?
Verfasst: 14 Mär 2018, 15:54
to disclose my intentions,
i built a custom opsiscript framwork (various opsiscripts with common code segments to be used in packages), and i need a template system to build basic opsi packages. i already have sort of built a custom IDE for opsi in jedit using various plugins, and it works, but it tends to be a real mess at times, also a rather awkward way to work with preexisting code segments/templates.
so i am looking for alternative ways, especially one i can easily impart on to my workmates.
after taking another look at opsi-setup-detector, in combination with package builder, it seems not too far from what i need, but it still lacks quite a bit.
thus i would like to ask if i may customize it (more specifically, for now i would like to provide a way to add custom setup detection patterns and additional usage cases and a way to import more then one setup into one package, and of course make it work with my existing opsiscript ecosystem). i would gladly share the results once i get it to a usable level.
if the answer to that is yes,
where can i find the source files for the current opsi-setup-detector release?
i found this: https://github.com/opsi-org/lazarus/tre ... updetector, but it appears to be a rather old version (4.0.5.124 if i got it right)
it appears to be written in freepascal using lazarus?
i built a custom opsiscript framwork (various opsiscripts with common code segments to be used in packages), and i need a template system to build basic opsi packages. i already have sort of built a custom IDE for opsi in jedit using various plugins, and it works, but it tends to be a real mess at times, also a rather awkward way to work with preexisting code segments/templates.
so i am looking for alternative ways, especially one i can easily impart on to my workmates.
after taking another look at opsi-setup-detector, in combination with package builder, it seems not too far from what i need, but it still lacks quite a bit.
thus i would like to ask if i may customize it (more specifically, for now i would like to provide a way to add custom setup detection patterns and additional usage cases and a way to import more then one setup into one package, and of course make it work with my existing opsiscript ecosystem). i would gladly share the results once i get it to a usable level.
if the answer to that is yes,
where can i find the source files for the current opsi-setup-detector release?
i found this: https://github.com/opsi-org/lazarus/tre ... updetector, but it appears to be a rather old version (4.0.5.124 if i got it right)
it appears to be written in freepascal using lazarus?