Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-pms
Navigation:
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-pms@g.o
From: Michał Górny <mgorny@g.o>
Subject: Describing USE=test in PMS?
Date: Wed, 7 Sep 2011 21:21:12 +0200
Hello,

As we all know, USE=test is a little special, being switched by Portage
FEATURES=test (and probably other PMs as well). Considering the fact
that it is used widely, I think we should consider describing it in PMS
or someplace else.

The exact rationale for this discussion is Johan's attempt of using
USE=test to decide what is installed with a package:

<jbergstroem> if tests would be installed through USE=test (should they
be a part of package?) we'd need to start setting other depends
( DEPEND=test? ( dev-python/subvertpy[test] ) )

Honestly, I'm not sure if this is really supposed to work. I personally
wouldn't risk using it. I suppose it could even start raising mayhem and
hurting puppies. But if we consider this just by looking at PMS, it is
absolutely fine.

Moreover, due to PMS USE=test would be just another USEflag, and
src_test() could be run with or without it. If we even aren't going to
describe USE=test thoroughly there, I think we should mention that
src_test() can be run only with USE=test set or something like that.

-- 
Best regards,
Michał Górny
Attachment:
signature.asc (PGP signature)
Navigation:
Lists: gentoo-pms: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
[PATCH] note that config and info don't save state either
Next by thread:
RFC: deprecate /usr/share/doc/$PF
Previous by date:
Re: [PATCH] note that config and info don't save state either
Next by date:
RFC: deprecate /usr/share/doc/$PF


Updated Jul 18, 2012

Summary: Archive of the gentoo-pms mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.