On Thu, Dec 29, 2016 at 8:30 PM, William Moreno <williamjmorenor(a)gmail.com>
wrote:
El 29/12/2016 9:00 p. m., "Dave Johansen" <davejohansen(a)gmail.com>
escribió:
On Thu, Dec 29, 2016 at 7:47 PM, William Moreno <williamjmorenor(a)gmail.com
> wrote:
> Just a wild idea: you can skip the docs!
>
> If the package includes it own documentation and this is to large, it
> must be in a docs sub package , current packaging guidelines do not block a
> package than do no include all docs available upstream, at less I think so.
>
I would like to have the docs include for my own uses. Some of the
machines I work on don't have internet access so being able to install the
docs locally is a big help.
This is new for me, a sphinx package than create a virtual env before call
the sphinx build
Looking at this file:
https://github.com/fmtlib/fmt/blob/master/doc/build.py
You can go to the end of file and see those lines:
if __name__ == '__main__':
create_build_env()
build_docs(sys.argv[1])
Just remove the call to the create_build_env() function (with a patch of
even with sed in %prep) and you can test to build with the system sphinx
version, this way at less you should now if the docs build with system lib,
having said that, this is Fedora! You will always will find a really up to
date version of sphinx in the Fedora repo!
I'll give that a try. Is there a way that I can disable network access in
my local mock to test that change?