> This makes it impossible to disable the man installation via --no-man, > doesn't it?
Technically, no. The previous (and documented) behaviour of --no-man was "Prevents the creation of man pages"; it had no effect on their installation. This may not be the best design but at the tail end of a release candidate cycle for 2.6.2 we're looking for things with a _very_ small behavior footprint. The change I proposed after talking it over with Nick takes things back to the way they were for non-MSWin systems and produces the desired results (no man page installation) for MSWin systems. If we want to change the definition of --no-man (no objection from me here), uncomment the man-page creation code, or anything else of that sort we should have a ticket for it targeted at Statler, and not slip it in as part of a fix for a fix for MS windows support. -- Markus ----------------------------------------------------------- The power of accurate observation is commonly called cynicism by those who have not got it. ~George Bernard Shaw ------------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
