RE: !! Take note !! CVS frozen !! RE: [Tcllib-devel] Tcllib Release

[Andreas K. <and...@Ac...>]

> At 21.05 +0200 2005-10-10, Andreas Kupries wrote:
> >>
> >> so why not do some whirling, indeed? So
> >> far I've mostly been dealing with the installer, but I thought I'd
better
> >> start typing things down before I forget...
> >>
> >> A first problem I had was that the installer doesn't handle
permissions.
> >
> >Do you mean by that the installer gets confused by permissions when
running,
> >or that it does not set permissions on the files it installs ?
>
> Primarily the former, but the latter would be good too.

Ok. Tcllib tracker, Bug or RFE report please.

> >> I understand it probably can't, but there could be some advice in
INSTALL.txt
> >> on how to deal with this.
> >
> >We do have commands in Tcl for this, see "file attributes".
>
> Oh, it's unusually inlined. Good! (Although practically it still wouldn't
> have worked, as my designated target area was originally root-only
> writable.)

Heh.

> >> Also it could try to catch the error (for me it
> >> was the [file mkdir tcllib1.8] that failed first) rather than just
error
> >> out completely.
> >
> >I am not sure here. The tcllib1.8 directory is important for all
> packages.
> >Erroring out does make sense IMHO.
>
> I meant "catch in order to provide a more readable error message".

Ah, ok. Thanks for the clarification.

> In
> particular if you're running in GUI mode, erroring out looks like an error
> in the installer rather than an error in the use of it.

Very good point. Tcllib tracker, Bug report please.

> >Actually warnings. Some of the section/subsection titles are not unique.
> >
> >
> >Eh ?? Interesting.
>
> I thought so too. Copying the message does not appear possible
> either (text
> widget bug, or just poor integration with system clipboard?), but retyping
> it in this mail as it was appearing on screen it turned out to be:
>
> Manpage warning (sectambig): unknown error code "sectambig" (for
> locale sv_se).

Ok. This a problem of doctools. It uses message catalogs for the error
messages, and did not find a catalog for your locale. I will have to re-read
manpages to see if there is a way to fall back into a default locale if the
actual one is not found.

The code tries to tell about the non-unique (sub)section titles, and then
finds that there is no message, and then reports that.

Tcllib tracker, Bug report please.

> >
> > [Later, after having browsed the
> >> installer.tcl code a couple of times, I see that the installer
> indeed just
> >> quits when done. When working in GUI mode, it should first ask the user
> >> whether (s)he wants to save the log window contents. An additional
> >> alternative could be to dump the log window contents to
> stdout, though.]
> >
> >The installer can be forced into non-gui mode, using -no-gui. In
> that mode
> >the log goes to stdout and can be captured.
>
> Yeah, but then I'd have to specify a _very_ large number of command line
> switches to get the locations right. I actually rather _prefer_ the GUI
> mode.

Ok. Tcllib tracker, RFE reports please, for 'have user exit GUI explictly',
and 'add button to write accumulated log into a file'.

> >
> >Hm. This might actually be platform dependent.
>
> Almost surely the locations are, but wouldn't the search order
> "user, local
> additions, vendor distribution" (which might be what in regular Unix?
> Perhaps ~, /opt, /usr) be logical also on other systems?

Not really. Remember, the order of paths in the tcl_pkgPath, and auto_path
does not matter for packages at all, at all. The standard behaviour of tclsh
when searching for an unknown package is to read all package indices in all
listed directories (and their subdirectories) and then choose the highest
version number possible within the constraints given to the 'package
require'.

So the order is really not relevant. Thus the Tcl core library may very well
use different orders on the various platforms.


> >From your paths I see that
> >you are on OS X. I tested this so far only on other Unix installations
> >(Linux, Solaris, ...) and Windows. For these the path chosen is quite
> >sensible.
>
> Could this be because there isn't much to choose from? Checking the Tcl on
> a local Linux machine, I find it is just /usr/lib (1 element, so the last
> is also the first),

Heh. Yes, that is of course also a possible reason why things are easy on
the other unix platforms. Only one candidate to look at. Forgot about that
actually.

--
	Andreas Kupries <and...@Ac...>
	Developer @ http://www.ActiveState.com, a division of Sophos
	Tel: +1 604 484 6491