Marius Mauch wrote:
On Fri, 18 Jul 2008 10:01:28 -0400
Doug Goldstein [EMAIL PROTECTED] wrote:
Olivier Crête wrote:
On Mon, 2008-07-14 at 18:01 -0400, Doug Goldstein wrote:
This brings out the fun of circular depends. I don't really know
how to address this but a lot of
On Mon, 21 Jul 2008 11:02:57 -0400
Doug Goldstein [EMAIL PROTECTED] wrote:
Marius Mauch wrote:
Now that's a big exaggeration. It _might_ be missing from world
updates (there are still many cases where it will be included), but
that's not the only available operation in portage.
Marius
Marius Mauch wrote:
On Mon, 21 Jul 2008 11:02:57 -0400
Doug Goldstein [EMAIL PROTECTED] wrote:
Marius Mauch wrote:
Now that's a big exaggeration. It _might_ be missing from world
updates (there are still many cases where it will be included), but
that's not the only available
Robert Bridge wrote:
On Fri, 18 Jul 2008 16:30:20 +0200
Arfrever Frehtes Taifersar Arahesis [EMAIL PROTECTED] wrote:
IMHO it would be better to teach users to explicitly specify
'@system' during updates, e.g. `emerge -uDN @system @world`.
Why not just re-instate the implicit dependency
On Fri, Jul 18, 2008 at 11:21 PM, Markus Rothe [EMAIL PROTECTED] wrote:
Robert Bridge wrote:
On Fri, 18 Jul 2008 16:30:20 +0200
Arfrever Frehtes Taifersar Arahesis [EMAIL PROTECTED] wrote:
IMHO it would be better to teach users to explicitly specify
'@system' during updates, e.g. `emerge
Olivier Crête wrote:
On Mon, 2008-07-14 at 18:01 -0400, Doug Goldstein wrote:
This brings out the fun of circular depends. I don't really know how to
address this but a lot of packages are going to have to be updated to
contain proper depends. i.e. C based apps will need
2008-07-18 16:01:28 Doug Goldstein napisał(a):
Olivier Cr�te wrote:
On Mon, 2008-07-14 at 18:01 -0400, Doug Goldstein wrote:
This brings out the fun of circular depends. I don't really know how to
address this but a lot of packages are going to have to be updated to
contain proper
Doug Goldstein wrote:
Yes. Adding libc everywhere is wrong. However, if you don't have one of
the packages listed here [1], your libc won't ever update.
Sure it will. When the version of libc you have installed is removed
from the portage tree you'll get bumped to the most recent
On Fri, 18 Jul 2008 16:30:20 +0200
Arfrever Frehtes Taifersar Arahesis [EMAIL PROTECTED] wrote:
IMHO it would be better to teach users to explicitly specify
'@system' during updates, e.g. `emerge -uDN @system @world`.
Why not just re-instate the implicit dependency of world on system?
Rob.
--
On Fri, 18 Jul 2008 10:01:28 -0400
Doug Goldstein [EMAIL PROTECTED] wrote:
Olivier Crête wrote:
On Mon, 2008-07-14 at 18:01 -0400, Doug Goldstein wrote:
This brings out the fun of circular depends. I don't really know
how to address this but a lot of packages are going to have to be
On Fri, 18 Jul 2008 16:21:24 +0100
Robert Bridge [EMAIL PROTECTED] wrote:
On Fri, 18 Jul 2008 16:30:20 +0200
Arfrever Frehtes Taifersar Arahesis [EMAIL PROTECTED] wrote:
IMHO it would be better to teach users to explicitly specify
'@system' during updates, e.g. `emerge -uDN @system
On Mon, 2008-07-14 at 18:01 -0400, Doug Goldstein wrote:
This brings out the fun of circular depends. I don't really know how to
address this but a lot of packages are going to have to be updated to
contain proper depends. i.e. C based apps will need
RDEPEND=virtual/libc. C++ packages will
With the new split in Portage where system set packages are not
considered in an emerge -auDNv world unless something in world
RDEPENDs on it brings about a few issues.
i.e. Portage implicitly has a run time dependency on app-arch/tar,
app-arch/bzip2, app-arch/gzip, app-arch/lzma due to the
13 matches
Mail list logo
