I recently tried to upgrade our seq package in our internal build tool
from seq 2.2.6 to seq 2.2.9, and came across an issue.
If I understood correctly, the 2.2.9 version introduces a more modern
RULES_SNCSEQ, which gets installed through CFG, and the old RULES_BUILD
sources the new RULES_SNCSEQ for backwards compatibility.
Hm, I see your point.
In principle, the seq architecture looks correct. It has a rules file for the seq build in configure and one for the downstream modules that gets installed in INSTALL_LOCATION/cfg. (And will be automagically sourced by all modules that declare SNCSEQ in one of their RELEASE files.)
But these two are not independent if one includes the other, which they should be. In a similar situation, I have just copied the rules block to be in both files, with comments explaining the situation. Not perfect, but it removes the dependency and will probably also avoid your issue.
Well, /cfg is an install directory. Putting sources there moves things towards ugly and obfuscated. (We still have that - traditional - situation in iocBoot, which is bad enough and we haven't resolved it cleanly yet.)
Cheers,
~Ralph
