Well, the theory goes something like this.
The Mandrake binary RPMS contain the raw docs directory (carryover from
previous pacckage specs).
With no compiled documentation.
So, since the documentation (in unassembled form) exists, I was trying to set
it up so that if the user had the necessary tools on hand, he/she could do a
DOCS_ONLY=1 make
in the Mandrake directory and get a compiled set of
subversion-doc.XYZ-1mdk.noarch.rpm or to bundle it in the main binary RPM.
So you see, it's not just for me. It's so that people *can* get a set of docs
w/ the binary RPM. I was trying to just do like it said in the instructions
for how to build the docs because, how else would I provide the same to
anyone else?
Does the release tarball contain compiled docs?
Is there a tarball with version specific compiled docs?
Should I package that instead?
Should I remove the uncompiled docs from the binary RPM that contains the
compiled executable?
I guess I was just trying the simplest solution, but didn't realize it
would create more problems.
Open to suggestions - I just need to be able to package the latest docs at
this point.
I think I've figured out how to set up the "compile your own docs" portion,
even though it seems to fail on my system through none of my doing. I will
update the README in the Mandrake area to reflect the steps necessary, for
anyone wanting to build one sometime prior to next release, and make sure
the log entries and everything else complies with HACKING.
Shamim Islam
BA BS
kfogel@collab.net wrote:
>
>Files, why are you trying to build the docs at all? It's much easier
>(for everyone :-) ) if you just download them from
>svnbook.red-bean.com. That's even what we do for our own releases.
>
>Ideally, it would be trivial to build the docs from source. But, due
>to circumstances beyond our control, it's not trivial, so we try to
>save everyone time by keeping prebuilt copies online. That effort is
>wasted whenever someone rebuilds them unnecessarily...
>
>-Karl
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: dev-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 23 19:17:33 2003