<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
Hi I found this conversation about the RPM Build error with the
/usr/share/doc path information.<br>
<br>
I'm trying to build the new freeradius-1.1.2 release over RHEL4 and I
got the same error. I'm not an expert with Linux and I would like to
know which is the best option to fix this problem.<br>
<br>
Thanks in advance<br>
<br>
Alberto Cruz<br>
Nicolas Baradakis wrote:<br>
<blockquote type="cite"
cite="mid20060329121048.GL26125@asuka.tech.sitadelle.com">
<pre wrap="">Duane Cox wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I noticed this too, that with 1.1.1 the docs are installed to
doc/freeradius and not doc/freeradius-1.1.1
</pre>
</blockquote>
<pre wrap=""><!---->
It has been discussed on the freeradius-devel mailing list: the
libraries and the executables are installed in version-independent
directories, therefore it's more consistent to have the docs under
share/doc/freeradius. BTW it's also the recommended location in the
Debian policy manual.
</pre>
<blockquote type="cite">
<pre wrap="">I'm not sure why this change came about, but can't a simple sed
script fix it? Then build your RPM.
sed -i '<a class="moz-txt-link-abbreviated" href="mailto:s@doc/freeradius@doc/freeradius-1.1.1@g">s@doc/freeradius@doc/freeradius-1.1.1@g</a>' doc/Makefile &&
sed -i '<a class="moz-txt-link-abbreviated" href="mailto:s@doc/freeradius/examples@doc/freeradius-1.1.1/examples@g">s@doc/freeradius/examples@doc/freeradius-1.1.1/examples@g</a>'
doc/examples/Makefile &&
sed -i '<a class="moz-txt-link-abbreviated" href="mailto:s@doc/freeradius/rfc@doc/freeradius-1.1.1/rfc@g">s@doc/freeradius/rfc@doc/freeradius-1.1.1/rfc@g</a>' doc/rfc/Makefile
</pre>
</blockquote>
<pre wrap=""><!---->
Perhaps adding this command in freeradius.spec could fix the problem:
sed -i "s@doc/freeradius@doc/freeradius-%{version}@" doc/Makefile doc/examples/Makefile doc/rfc/Makefile
However, I think it'd be more elegant to add an option --docdir to
configure and update the makefiles to use that.
</pre>
</blockquote>
</body>
</html>