On Tue, Sep 17, 2013 at 09:46:05AM -0400, al davis wrote: > It was initially but it may have been an incorrect decision. > The justification was that new plugins may want something > completely different and plans to make outputs pluggable.
in the long run... > To be consistent, probably s__.h should have been left in apps, > so you copy it to new plugins. in any case it would be better to have (a) librar(y/ies) that match the installed include headers... > [..] > Wishy-washy answer because I am not sure the decision was > correct. why not make the transition explicit: everything that is not yet a plugin but used by the s_* could go into libgnucap_output.so? regards felix _______________________________________________ Gnucap-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnucap-devel
