Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. Summary: Review Request: subversion-api-docs https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=177483 ------- Additional Comments From bojan@xxxxxxxxxxxxx 2006-03-06 04:57 EST ------- > Does the subversion-api-docs-doxygen.conf file come from upstream somewhere? Yes. We can link into the correct branch/tag of SVN repository of Subversion. > Requires should be on subversion rather than subversion-devel People that use this package are developers that use Subversion APIs. It is unlikely they will be developing software that uses Subversion APIs without wanting to have subversion-devel installed. It make sense that this package pulls in the -devel package. > BuildRequires subversion-devel and the Requires should require the full EVR Documentation goes into packagename-%{version} subdirectory. APIs of Subversion don't change mid major release. The documentation in the newer version/release may be a bit better (i.e. more accurate) but that's not critical for the API or functioning of the package. That's why release info isn't necessary. > How are you going to keep this package synced up with Core's subversion? Well, that is a good question. AFAIK, FE packages are rebuilt by hand. The maintaner just needs to update the package when required - a situation that is no different to many other packages from FE that may depend on FC packages that get bumped up, therefore creating an upgrade problem. This can be fixed like this: Requires: subversion-devel >= %{version} Then we can also own: %doc %dir %{_docdir}/subversion-%{version} To make sure this directory gets whacked when the old version of subversion-api-docs finally gets upgraded. > We would want to include a copy of subversion's LICENSE in this case. Sure. Again, we can point to the relevant file in Subversion SVN repository. -- Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
