On Thu, Nov 07, 2002 at 04:13:44PM +0000, Mikhael Goikhman wrote: > On 07 Nov 2002 14:44:42 +0100, Dominik Vogt wrote: > > > > On Thu, Nov 07, 2002 at 01:27:32PM +0000, Mikhael Goikhman wrote: > > > On 07 Nov 2002 14:04:59 +0100, Dominik Vogt wrote: > > > > > > > > On Thu, Nov 07, 2002 at 12:56:54PM +0000, Mikhael Goikhman wrote: > > > > > > > > > > Actually, if the only reason is to give an example as you correctly > > > > > pointed, they should not be installed to /usr/bin (or similar > > > > > $bindir). > > > > > 1) They may be be distributed and a link in the man page to > > > > > ftp://ftp.fvwm.org/pub/fvwm/devel/sources/utils/ may be given. > > > > > 2) Or they may be installed to $docdir (I hope to add it later anyway) > > > > > together with README, INSTALL.fvwm etc.. Currently this may be > > > > > $datadir. > > > > > > > > > > If any of this is a good solution to you, they should not be in bin/, > > > > > but in utils/. > > > > > > > > Theoretically yes, but they should still be installed for > > > > backward compatibility. People may rely on the being installed. > > > > (But I'm not sure wheter they were installed in previous > > > > versions). > > > > > > I don't think they were ever installed, maybe during several days between > > > 2.3.1 and 2.3.2: > > > > > > Sun May 9 02:43:02 1999 Steve Robbins <[EMAIL PROTECTED]> > > > > > > * utils/Makefile.am: don't install fvwm_make_browse_menu.sh until > > > we have some consensus on _where_ to put it. > > > > > > They are not distributed since 2.3.7, I think. > > > > I must have missed it back then. Personally, I see no problem > > installing them in bindir. > > I see a serious problem in doing this. It is one thing to give an example > of creating user's menus and another to suggest a user to use these > scripts and rely on them later. Do you want quantity or quality? > Maybe we should in addition install into everyone's /usr/bin a C version > and an awk version that do opendir and print all files, just to show that > users may do it in these languages too? > > No, we need to support one very configurable script, so most of the users > would just use it and not think about recreating such script themselves. > Let's do what we agreed to, distribute and possible install to docdir. > > > > As for me, I prefer simply to give an url. Run for example: > > > > > > fvwm-perllib man tutorial > > > > > > There is a link to test modules. they are not even distributed, > > > although it is pretty difficult to learn perllib without them. > > > > I am not sure this is a wise decision. Not everyone has net > > internet access. As they seem to serve documentation purposes > > only, they should be installed somewhere in docdir. > > Maybe later I will see good reasons to distribute these files. Nowadays > every programmer has an internet, at least a web.
Well, I think we will never agree on this. My foremost goal is portability. I just can't make myself to see "internet access" and perl as being available everywhere all the time. People are struggling with routing, dial in problems and dead links every day. If you think it bloats the tarball and the installation we can make another cvs module "fvwm-docs" that contains the supporting documentation. Bye Dominik ^_^ ^_^ -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
