Hi Dermot Another possibility would be to create a new directory, perhaps man1t, for the Tcl and Tk built-ins. That would avoid the name conflicts.
Are you planning to deliver the Tcl scripting language and Tk GUI toolkit into Solaris Express, or just into OpenSolaris? If so, do you have a sponsor? Thanks Doug > X-Original-To: docs-discuss at opensolaris.org > Delivered-To: docs-discuss at opensolaris.org > From: Dermot McCluskey <dermot.mccluskey at sun.com> > To: docs-discuss at opensolaris.org > Mime-Version: 1.0 > Content-Transfer-Encoding: 7bit > X-OpenSolaris-URL: http://www.opensolaris.org/jive/message.jspa?messageID=121006&tstart=0#121006 > Subject: [docs-discuss] Re: Guidance wanted for Tcl/Tk man pages > X-BeenThere: docs-discuss at opensolaris.org > X-Mailman-Version: 2.1.4 > List-Id: General documentation discussion and requests to contribute documentation <docs-discuss.opensolaris.org> > List-Unsubscribe: > <http://mail.opensolaris.org/mailman/listinfo/docs-discuss>, <mailto:docs-discuss-request at opensolaris.org?subject=unsubscribe> > List-Archive: <http://mail.opensolaris.org/pipermail/docs-discuss> > List-Post: <mailto:docs-discuss at opensolaris.org> > List-Help: <mailto:docs-discuss-request at opensolaris.org?subject=help> > List-Subscribe: <http://mail.opensolaris.org/mailman/listinfo/docs-discuss>, <mailto:docs-discuss-request at opensolaris.org?subject=subscribe> > > Doug, > > Thanks for your responses so far. > > I'm fine with moving the man3 stuff to man3tcl and man3tk. But I'm still not > sure about moving mann to man1: > > > These built-in commands would go into section 1, User Commands. For those > > commands that have the same name as a Solaris built-in, you could modify > > the existing page to add the new functionality, if > > that page has already been opensourced. > > Between Tcl and Tk there are 179 of these manpages. And of these, > 28 name-clash with existing section 1 manpages: > > break.1 case.1 cd.1 continue.1 error.1 eval.1 exec.1 exit.1 expr.1 file.1 > for.1 foreach.1 glob.1 history.1 if.1 join.1 pack.1 proc.1 pwd.1 read.1 > return.1 set.1 source.1 split.1 switch.1 time.1 unset.1 while.1 > > and several of these are just pointers to other pages like shell_builtins.1. > (also how do I tell which if these have already been opensourced). > > So that's a lot of pages to edit and seems a very messy solution. > Is that really the best way to tackle this? > > - Dermot > > > This message posted from opensolaris.org > _______________________________________________ > docs-discuss mailing list > docs-discuss at opensolaris.org
