On Mon, Jan 19, 2004 at 08:26:57AM +0000, Tom Payne wrote:
> 3. Minor typo in README (system.mk, not ssystem.mk).
Already fixed in the snapshots.
> 4. system.mk says libtool >= 1.4.0 is required, but README says libtool >=
> 1.4.3 is required. Which is it?
README says 1.4.0, system.mk 1.4.3. I have only tested 1.4.3, but as far
as I know, 1.4.0 should work.
> 5; README and README.autoconf should be merged into a single file, or
> possibly separated into README and INSTALL with suitable changes.
> README.autoconf was written for when the autoconf script wasn't part of the
> ion distribution.
I think a separate README.autoconf is okay, but should probably only
contain the options and notes for different platforms. I've never liked a
separate INSTALL file, but don't want to crowd the README.
> I would like to see:
> ion2-<date>
> and the binaries, directory names, etc. similarly named. Currently the
> config directory is called ~/.ion2, but everything else is called ion.
Ideally, Ion would be installed in '/local/apps/ion-2-date' or something
like that, and the version would be there in the path. But for user
configuration files we must have the version in the user-etc path.
The user configuration file path should have been ~/.ion-2, but I hadn't
decided the final name of the package at that point and am not going the
user configuration file path now.
> Renaming everything to ion2 would be consistent, and theoretically allow
> ion2 and the old ion stable (which some people still use) to be installed
> on the same machine without conflict.
Any number of versions could be installed on the same machine at the
same time given a sane directory structure instead of the *nix standard
everything in one basket structure.
> Finally, is there any reason why the dock module is not automatically
> loaded in ion?
I consider the dock an essential part of PWM, but an extra to Ion
that not everyone might want. I in particular still use just a shell
script on one workspace for all the monitoring tasks. I have added
a commented-out line to load it in the configuration file, though.
> (It is in pvm). How about adding include("dock-draw.lua") to
> the example look-*.lua files? Doing so would not harm non-dock users?
Is there any actual need to do so? Aren't the defaults the same? I'd
rather keep the files as concise as possible for easier modification.
(Some of the files are auto-converted and contain many redundant
settings.) The dock options should be added in the documentation,
though.
--
Tuomo
