Re: Building the documentation of a package that must already be installed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Sep 2, 2018 at 10:39 AM Dan Čermák <dan.cermak@xxxxxxxxxxxxxxxxxxx> wrote:
Hi list,

I recently wanted to update the Fedora package of gcovr
(https://github.com/gcovr/gcovr). However, I have hit the following
problem: the gcovr doc is build via sphinx, but it won't build unless
gcovr is installed, both the binary and the python package.

Can't you fake some paths to python lib and binary so that documentation is using those (built but not installed)?
 
A little background: gcovr is a Python package and is build & installed
via setuptools. This means that before `setup.py install` has run, the
package is not available to Python and the binary gcovr was not created
yet. It would be ideal for the documentation to build it after the
%install section (e.g. in the %check section, but that is certainly
prohibited).


Cheers,

Dan
_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx
--

-Igor Gnatenko

_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/packaging@xxxxxxxxxxxxxxxxxxxxxxx

[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux