aalib [LSARC/2009/302 FastTrack timeout 05/21/2009]

Jim Walker James.Walker at sun.com
Thu May 14 22:20:58 PDT 2009


John Fischer wrote:
> Fan,
> 
> The files within bin all seem (with the exception aaconfig-lib)
> to be example programs for aalib.  In fact the man page for aafire
> states:
> 
>      aafire, aainfo, aasavefont, aatest - aalib example programs
> 
> So I am not sure why they are being included on Solaris with this
> project.  Or at least I am not sure why they are being include in
> /usr/bin.  Perhaps /usr/demo/aalib would be more appropriate.  If
> they are included in /usr/bin I would also expect the man page to
> be delivered with an Attributes section.  These also do not seem
> like they should be Uncommitted but Volatile at best.  If these
> are in /usr/demo then they are "Not an Interface".  Also if you
> go the /usr/demo route you might consider including the source
> code for these demos along with the binary.
> 
> aaconfig-lib is a utility that makes sense to have in /usr/bin
> for developers as it informs them of useful information.  It
> should also have a man page with an Attributes section.

I agree. /usr/demo is better and Li Fan can add an aaconfig-lib
manpage.

Li Fan and I discussed this but he want to try for the more
"familiar" location.

Li Fan,

Can you confirm these changes are ok with you?

Cheers,
Jim



More information about the opensolaris-arc mailing list