> > > I think you'd be better off modifying the mangler, but restricting your
> > > changes to mangle_manpage(), which could make sure that there are no
> > > blank lines prior to .TH.
> >
> > Ah, you mean keep the CDDL removal as it is, but add code for removing
> > blank lines in page header?
>
> Yup. Having written the code for CDDL removal for the IPS gate, I know
> that doing that well is quite tricky, so I think cleanup afterwards is
> probably a bit easier, and safer to boot.
>
> > > Shouldn't be all that hard, though obviously a bit of testing will be
> > > required beyond just ntp. Shouldn't even have to do a full build of
> > > each component, just the appropriate mangle target.
> >
> > How does one do such thing?
>
> For ntp, I did
>
> gmake $PWD/build/manifest-i386-ntp.mangled
Hmm, I think I'll run full nightly, change the code, run full nightly
again and manually parse the repo contents to compare which man pages
were changed. Or even better, "unpack" repository into real proto area
and run diff over previous and new one. That seems to me to be the
easiest way.
> You can do that before and after the change to the mangler and diff the
> resulting files to make sure the changes are what you expect. Getting the
> exact names of all the .mangled files is the harder part, but you can
> probably take the gate's nightly build, find all of those files (should be
> reasonably easy), and make them one by one with a simple script.
7069662 Userland is missing tools/process to track changes in proto areas
Thank you
--
Vlad
_______________________________________________
userland-discuss mailing list
userland-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
