gensch_at_zk3.dec.com writes:
> I think it would be a useful thing if fvwm could support installable
> packages. A package would be a set of related files needed to
> configure fvwm in some special way.
>
> What I have in mind is to add a new command in fvwm's configuration
> file syntax:
...
> This package directory should be stored somewhere within the
> ModulePath (or we could also create a 'PackagePath' keyword for this
> purpose!), and it could be read by the command:
>
> AddPackage Win95
>
...
>
> What do people think of this idea?
Sounds like a good idea. I wonder if it is a good idea to overload the
modulepath for this, since a package really isn't a module. I'd prefer using
PackagePath. For example, I typically have my modules somewhere in my ~/bin
hierarchy, since they are platform dependant binaries (I have subdirectories
in ~/bin for each OS/ARCH combination I use), but would probably want my
packages in a ~/.fvwm directory.
--
Brady Montz
bradym_at_cs.arizona.edu
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Wed May 20 1998 - 11:10:24 BST