From: Brian Jackson <iggy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] splitting build deps out from depends
Date: Tue, 05 Jul 2005 20:59:17 -0500 [thread overview]
Message-ID: <42CB3AF5.4080004@gentoo.org> (raw)
In-Reply-To: <1120614402.8314.87.camel@lycan.lan>
Martin Schlemmer wrote:
<snip>
>>
>>Big picture here:
>>* BDEPEND does nothing now, so don't worry about it if you don't want to
>>* in the future it will make other things possible
>>* give the man problems you see with the proposal, not just tell him that
>>portage doesn't handle it right now... I think out of anyone, he knows what
>>portage does and doesn't handle
>>
>
>
> I did ask Brian in another reply how he thought to implement it.
>
> This one however I read as Drake saying/asking that we should start
> doing it now, and I tried to explain why we could not up until now, and
> still cannot. Correct me if I interpreted it wrongly.
>
>
I don't know why we can't start now if we want. BDEPEND will be silently
ignored, so current versions of portage will just be blissfully ignorant.
Am I missing something?
Some of us think we can't start now, others think we can. I was under the
impression from ferringb that we could.
--Iggy
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-06 2:02 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-01 16:25 [gentoo-dev] splitting build deps out from depends Brian D. Harring
2005-07-01 17:49 ` Mike Frysinger
2005-07-01 18:03 ` Diego 'Flameeyes' Pettenò
2005-07-01 18:11 ` Brian D. Harring
2005-07-01 18:30 ` Mike Frysinger
2005-07-01 18:42 ` Brian D. Harring
2005-07-01 18:46 ` Brian D. Harring
2005-07-01 18:53 ` Diego 'Flameeyes' Pettenò
2005-07-01 19:10 ` Brian D. Harring
2005-07-01 20:25 ` Paul de Vrieze
2005-07-05 9:39 ` Martin Schlemmer
2005-07-07 11:56 ` John Myers
2005-07-07 19:44 ` Kito
2005-07-07 20:45 ` Diego 'Flameeyes' Pettenò
2005-07-09 9:28 ` Jason Stubbs
2005-07-01 18:37 ` Diego 'Flameeyes' Pettenò
2005-07-01 22:59 ` Drake Wyrm
2005-07-02 1:16 ` Kito
2005-07-04 0:18 ` Brian D. Harring
2005-07-09 9:28 ` Jason Stubbs
2005-07-05 10:48 ` Martin Schlemmer
2005-07-05 23:17 ` Brian Jackson
2005-07-06 1:46 ` Martin Schlemmer
2005-07-06 1:59 ` Brian Jackson [this message]
2005-07-06 2:39 ` Martin Schlemmer
2005-07-06 17:08 ` Brian D. Harring
2005-07-07 13:29 ` Martin Schlemmer
2005-07-09 9:28 ` Jason Stubbs
2005-07-09 9:45 ` Diego 'Flameeyes' Pettenò
2005-07-09 9:28 ` Jason Stubbs
2005-07-09 10:17 ` Martin Schlemmer
2005-07-09 9:28 ` Jason Stubbs
2005-07-09 9:47 ` Diego 'Flameeyes' Pettenò
2005-07-09 10:20 ` Martin Schlemmer
2005-07-09 11:45 ` Diego 'Flameeyes' Pettenò
2005-07-09 12:01 ` Martin Schlemmer
2005-07-09 12:08 ` Diego 'Flameeyes' Pettenò
2005-07-09 12:37 ` Stephen Bennett
2005-07-09 12:41 ` Martin Schlemmer
2005-07-09 12:46 ` Diego 'Flameeyes' Pettenò
2005-07-09 13:05 ` Martin Schlemmer
2005-07-09 13:11 ` Diego 'Flameeyes' Pettenò
2005-07-09 14:10 ` Martin Schlemmer
2005-07-09 19:19 ` Kito
2005-07-01 17:58 ` Diego 'Flameeyes' Pettenò
2005-07-01 18:35 ` Maurice van der Pot
2005-07-01 18:45 ` Brian D. Harring
2005-07-01 18:56 ` Maurice van der Pot
2005-07-01 19:12 ` Brian D. Harring
2005-07-01 19:19 ` Maurice van der Pot
2005-07-02 3:48 ` [gentoo-dev] " Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42CB3AF5.4080004@gentoo.org \
--to=iggy@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox