Ken Williams <[EMAIL PROTECTED]> writes: > I'd like to pick up this thread again if possible. Splitting out a > set of developer's tools from the installer's tools is something I'd > really like to see happen.
Yes! > I'm not really sure where to start, though, or what the solution > should look like. Have you thought about it any more? I'll throw in a couple of my pet peeves here. First of all, it is necessary to realize that there is a fundamental difference between building and installing. Roughly speaking, 'building' takes source and produces (compiles, builds, prepares) an install kit. 'Installing' takes this kit and installs (puts the files into place) it. While you can build on almost any system, it is quite normal for an install kit to be dedicated to a subset of systems. Sometimes you even need an install kit for each different platform that the deliverable should run on. Important distinction is that to install, you don't need tools other than basic file management. To build, you may need compilers, libraries and other dedicated tools like make. Some systems don't have these. Although I usually focus on the aspect of application building and installing I'll restrict myself here to modules. We have Module::Build for building, Module::Install would be a good candidate for module installing. Since it would be nice if M::B could install as well, M::I could be a component of M::B, as long as it is possible to use it on its own. -- Johan
