Toby Thain writes:
> Having docs as a separate package enabled/disabled by --with[out]-
> docs seems fairly commonplace. Without that, you end up requiring the
> tools. I favour this approach:
> * add the switch
> * if switch not used, and tools are available, always build docs
> * if tools not available, or package disabled by switch, skip
> building docs (currently, build simply fails)
>
> That seems to do the right thing for everyone?
>
Not quite. It does not install prebuilt docs for those who lack the
tools. I mean, the autotools know the concept of maintainer-built
files. These files are packed into the tarball and are available on
the target machine for further processing or for installation. I see
this as a valid mechanism to distribute docs which need more
processing than a text file. Therefore I still want to achieve this
behaviour:
- if you use a tarball, the prebuilt docs should be installed. As the
files are already there, there should not be any need to rebuild
anything.
- if you build from CVS sources, attempt to build the docs unless the
tools are missing or the user decided not to build the docs
(--disable-docs)
regards,
Markus
--
Markus Hoenicka
markus.hoenicka@xxxxxxx
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
|
