Re: Sphinx builds always write to the source directory

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

 



On Tue, 31 Jan 2017 09:32:20 +0200
Jani Nikula <jani.nikula@xxxxxxxxxxxxxxx> wrote:

> On Tue, 31 Jan 2017, Ben Hutchings <ben@xxxxxxxxxxxxxxx> wrote:
> > I'm having trouble with the Debian packaging of kernel documentation. 
> > We try to build everything in a separate output directory (underneath
> > debian/build), but the new Sphinx-based build system writes to the
> > source directory.
> >
> > Firstly, Python creates bytecode files alongside the module sources. 
> > This could be avoided by setting environment variable
> > PYTHONDONTWRITEBYTECODE=1, at the expense of requiring recompilation
> > more often.  
> 
> I've sent the patch a few times.
> 
> http://lkml.kernel.org/r/1479916579-17151-1-git-send-email-jani.nikula@xxxxxxxxx

It doesn't appear that you sent it to me, though, and I don't recall
having seen it.  Care to resend, and I'll pick it up?

jon
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux