On Fri, 2003-12-05 at 19:01, Mike Avery wrote:
> >
> >
> >include "Makefile.config"
> >
> >and then operating on that file instead, i.e. leave all the logic in the
> >Makefile and system-config-nis only fiddles with Makefile.config?
> >
> >Nils
> >
> >
>
> How would you propose to do this be included without possibly causing
> confusion? Truncating the Makefile and inserting a blurb about
> consulting Makefile.config?
Exactly. This way, newer NIS packages can easily update "Makefile" (the
logic) while the configuration gets preserved.
> Maybe I'm not seeing something here. If this is the case, please
> educate me.
I don't know what you mean.
> As it stands, I read in the entire Makefile into a list, and identify
> those list elements which contain valid directives (above the DON'T
> CHANGE warning), and placing those directives into the correct widgets
> in the GUI for alteration. When cahnges are saved, I overwrite changed
> list elements and write the list out to Makefile.
With logic separated from configuration, you just read/write the config
file which additionally gives the packaging advantages I mentioned
above.
Nils
--
Nils Philippsen / Red Hat / nphilipp@xxxxxxxxxx
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- B. Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
Attachment:
signature.asc
Description: This is a digitally signed message part