Re: [gentoo-dev] crossdev: installing _host_ build dependencies not automatic?

2017-05-13 Thread Paweł Hajdan , Jr .
On 03/05/2017 17:56, Alexis Ballier wrote:
> From man emerge:
> 
>--root-deps[=rdeps]
>   If  no argument is given then build-time dependencies of
>packages for ROOT are installed to ROOT instead of /.  If the
>rdeps argument is given then discard all build-time dependencies
>of packages for ROOT.  This option is only meaningful when used
>together with ROOT and it should not be enabled under normal
>circumstances!

Ah, I didn't know about that. Thanks!

>   Does not affect EAPIs that support HDEPEND.  Experimental
>   EAPI 5-hdepend provides HDEPEND as a new means to adjust
>   installation into "/" and ROOT.  If ebuilds using EAPIs
>   which do not support HDEPEND are built  in  the same
>   emerge run as those using EAPIs which do support HDEPEND,
>   this option affects only the former.

Curious - what's the status of HDEPEND for the main tree?

Paweł



signature.asc
Description: OpenPGP digital signature


Re: [gentoo-dev] Should Sphinx really depends on PYTHON_COMPAT/PYTHON_USEDEP for `dev-python/*` ebuilds?

2017-05-13 Thread Michał Górny
On pią, 2017-05-12 at 17:42 -0700, Daniel Campbell wrote:
> On 05/11/2017 12:51 AM, Michał Górny wrote:
> > In fact, I'm personally leaning towards not building docs at all
> > in ebuilds. It's practically a wasted effort since most of the time
> > users read docs online anyway.
> 
> I believe that's a little myopic; a user (or even developer) may not
> have Internet access all the time, or may not have it in their primary
> development environment. Having a copy of the docs locally (the entire
> point of USE="doc") is super valuable to have when you're away from the
> network. I'm sure I'm not alone as one of the people who uses the flag
> and appreciates the work that goes into making sure said flag works.
> 
> Sure, we could yank out every single USE="doc", but then we lose a nice
> feature of the tree and users are back to either (a) trawling the Web to
> find the project site, then hope they have docs in a separate download,
> or (b) we end up with foo+1 packages, one extra for any package that has
> documentation. Neither are particularly good solutions; Debian has done
> the latter and it results in a huge number of packages for little gain.

The Python team mostly focuses on providing packages for dependencies of
other Gentoo packages, not direct Python development. We do not have
the manpower to go above that.

-- 
Best regards,
Michał Górny


signature.asc
Description: This is a digitally signed message part