Lets say a package foo depends on bar, both at compile time and run time.
Shouldn't DEPEND _and_ RDEPEND of the foo package reflect that
dependency? I usually set DEPEND=$RDEPEND ... or vice-versa (depending
on which is the most demanding). Am I utterly wrong here?
I know that when a package is
On Tue, Apr 25, 2006 at 09:53:58AM +0300, Alin Nastac wrote:
Lets say a package foo depends on bar, both at compile time and run time.
Shouldn't DEPEND _and_ RDEPEND of the foo package reflect that
dependency? I usually set DEPEND=$RDEPEND ... or vice-versa (depending
on which is the most
Alin Nastac wrote:
Lets say a package foo depends on bar, both at compile time and run time.
Shouldn't DEPEND _and_ RDEPEND of the foo package reflect that
dependency? I usually set DEPEND=$RDEPEND ... or vice-versa (depending
on which is the most demanding). Am I utterly wrong here?
I know
Thilo Bangert has decided to return after an extended vacation (previously
with Gentoo in 2002).
The fun life of studying all over the world has finally caught up with him and
really needs some bug and ebuild theropy (particulary of the net-mail
variety).
Please welcome Thilo to theropy as he
Hopefully he signs some contracts to never leave again...
Re-Welcome on board :)
signature.asc
Description: OpenPGP digital signature
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
2002? Vintage! Welcome back.
Daniel wrote:
Thilo Bangert has decided to return after an extended vacation (previously
with Gentoo in 2002).
The fun life of studying all over the world has finally caught up with him
and
really needs some bug
Hello here,
I'd like to see some clarification of intended doc use flag usage, so
that we wouldn't force users to download/install 40+ megs of docs for a
~3 meg package, with the only reason being that USE=doc is for developer
documentation only. [1]
And no, I don't think we need yet another use
On 25/04/06, Jakub Moc [EMAIL PROTECTED] wrote:
Hello here,
I'd like to see some clarification of intended doc use flag usage, so
that we wouldn't force users to download/install 40+ megs of docs for a
~3 meg package, with the only reason being that USE=doc is for developer
documentation
Could a simple USE flag (Such as branding) be implemented, which if set, will
pull in and configure gentoo themes when a package is compiled? This could be
unset by default, meaning most users would not be effected by this.
--
gentoo-dev@gentoo.org mailing list
Matthew Gaule wrote:
Could a simple USE flag (Such as branding) be implemented, which if set, will
pull in and configure gentoo themes when a package is compiled? This could be
unset by default, meaning most users would not be effected by this.]
If most users are unaffected by the change,
It could be set as a default use flag and those not wanting any
branding can add '-branding' to their make.conf
Regards,
On 4/25/06, Donnie Berkholz [EMAIL PROTECTED] wrote:
Matthew Gaule wrote:
Could a simple USE flag (Such as branding) be implemented, which if set,
will
pull in and
11 matches
Mail list logo
