On Wed, Feb 4, 2009 at 3:02 PM, Grant wrote:
> When this was asked a few weeks ago someone then asked why
> --with-bdeps Y isn't the default? This seems to burn nearly everyone
> once in awhile.
>
Because using --with-bdeps y causes unnecessary compilation
On Wednesday 04 February 2009 23:02:38 Grant wrote:
> I think I've gotten to the bottom of my boost problem. I have
> rb_libtorrent installed which requires >=dev-libs/boost-1.35, meaning
> boost needs to be in package.keywords. If I remove boost from
> package.keywords, should portage tell me th
On Wed, Feb 4, 2009 at 1:02 PM, Grant wrote:
>
> I think I've gotten to the bottom of my boost problem. I have
> rb_libtorrent installed which requires >=dev-libs/boost-1.35, meaning
> boost needs to be in package.keywords. If I remove boost from
> package.keywords, should portage tell me there
When this was asked a few weeks ago someone then asked why
--with-bdeps Y isn't the default? This seems to burn nearly everyone
once in awhile.
>>> Because using --with-bdeps y causes unnecessary compilation of packages
>>> that don't need t0 be changed.
On Tue, Feb 3, 2009 at 5:42 PM, Grant wrote:
>>> When this was asked a few weeks ago someone then asked why
>>> --with-bdeps Y isn't the default? This seems to burn nearly everyone
>>> once in awhile.
>>>
>> Because using --with-bdeps y causes unnecessary compilation of package
>> When this was asked a few weeks ago someone then asked why
>> --with-bdeps Y isn't the default? This seems to burn nearly everyone
>> once in awhile.
>>
> Because using --with-bdeps y causes unnecessary compilation of packages
> that don't need t0 be changed. They won't b
> When this was asked a few weeks ago someone then asked why
> --with-bdeps Y isn't the default? This seems to burn nearly everyone
> once in awhile.
>
Because using --with-bdeps y causes unnecessary compilation of packages
that don't need t0 be changed. They won't be used
On Tue, Feb 3, 2009 at 5:12 PM, Dale wrote:
> Grant wrote:
When this was asked a few weeks ago someone then asked why
--with-bdeps Y isn't the default? This seems to burn nearly everyone
once in awhile.
>>> Because using --with-bdeps y causes unnecessary compilation of packages
Grant wrote:
>>> When this was asked a few weeks ago someone then asked why
>>> --with-bdeps Y isn't the default? This seems to burn nearly everyone
>>> once in awhile.
>>>
>> Because using --with-bdeps y causes unnecessary compilation of packages
>> that don't need t0 be changed. They won't
On Tue, Feb 3, 2009 at 4:51 PM, Grant wrote:
>>> When this was asked a few weeks ago someone then asked why
>>> --with-bdeps Y isn't the default? This seems to burn nearly everyone
>>> once in awhile.
>>
>> Because using --with-bdeps y causes unnecessary compilation of packages
>> that don't need
>> When this was asked a few weeks ago someone then asked why
>> --with-bdeps Y isn't the default? This seems to burn nearly everyone
>> once in awhile.
>
> Because using --with-bdeps y causes unnecessary compilation of packages
> that don't need t0 be changed. They won't be used again until the
>
On Tue, 3 Feb 2009 12:32:15 -0800, Mark Knecht wrote:
> When this was asked a few weeks ago someone then asked why
> --with-bdeps Y isn't the default? This seems to burn nearly everyone
> once in awhile.
Because using --with-bdeps y causes unnecessary compilation of packages
that don't need t0 be
On Tue, Feb 3, 2009 at 2:32 PM, Mark Knecht wrote:
> On Tue, Feb 3, 2009 at 12:23 PM, Neil Bothwick wrote:
>> On Tue, 3 Feb 2009 11:29:01 -0800, Grant wrote:
>>
>>> Is portage supposed to pick up on this with 'emerge -avDuN world'?
>>
>> Not if these are build-time dependencies, in which case the
On Tue, Feb 3, 2009 at 12:23 PM, Neil Bothwick wrote:
> On Tue, 3 Feb 2009 11:29:01 -0800, Grant wrote:
>
>> Is portage supposed to pick up on this with 'emerge -avDuN world'?
>
> Not if these are build-time dependencies, in which case they'll only be
> picked up when you use --with-bdeps y.
>
> T
On Tue, Feb 3, 2009 at 2:23 PM, Neil Bothwick wrote:
> On Tue, 3 Feb 2009 11:29:01 -0800, Grant wrote:
>
>> Is portage supposed to pick up on this with 'emerge -avDuN world'?
>
> Not if these are build-time dependencies, in which case they'll only be
> picked up when you use --with-bdeps y.
>
> Th
On Tue, 3 Feb 2009 11:29:01 -0800, Grant wrote:
> Is portage supposed to pick up on this with 'emerge -avDuN world'?
Not if these are build-time dependencies, in which case they'll only be
picked up when you use --with-bdeps y.
This is becoming a VFAQ.
--
Neil Bothwick
If weather bureaus wer
I do a daily 'emerge -avDuN world' to keep everything up to date, but
I've noticed it doesn't always find everything. As an example:
# emerge -avDuN world
These are the packages that would be merged, in order:
Calculating dependencies... done!
Total: 0 packages, Size of downloads: 0 kB
Nothing to
17 matches
Mail list logo
