From: Tony Clark <tclark@telia.com>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] emerge -u program
Date: Thu, 1 May 2003 10:42:17 +0200 [thread overview]
Message-ID: <200305011042.24128.tclark@telia.com> (raw)
In-Reply-To: <200305010832.47633.mike-list@wakerly.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thursday 01 May 2003 10.32, mike wakerly wrote:
> On Thursday 01 May 2003 07:51 am, Tony Clark wrote:
> > My glibc and gcc aren't in stable release yet but when I went to upgrade
> > a program it wanted to downgrade these. I can understand this behaviour
> > when using emerge -u world but it doesn't make sence IMHO for a specific
> > program. Not sure I can call it a bug, but it seems strange behaviour.
>
> You might want to use -U; it's the upgrade-only flag.
I know how to solve the problem, but it isn't my point. My question is should
emerge -u someprogram be allowed to down grade other programs in the process
unless DEPEND < current_installed_versions are actually specificed in the
ebuild. No problem with world behaviour, there I believe it does the correct
thing.
tony
- --
Contract ASIC and FPGA design.
Telephone +46 702 894 667
http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x633E2623
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iQCVAwUBPrDd8GkjRGZD9pCjAQKitgQAuMIONPfIghHwgM1xp+AhaC1ry/5ERnYV
KRasXVop0GrUioRxMoq5PwGbxXZZd2tiALZY/KTaNRyoabAcF4e/E3MUbeW2bhS+
IecVLtJpuujY/rwS2arfGbQiHqIqoqPwuPmMQlGzWgiAXZIM/6bx/0uqXpeqKb2g
pq5aPoowHu0=
=P/f7
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-05-01 8:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-01 7:51 [gentoo-dev] emerge -u program Tony Clark
2003-04-30 18:21 ` Alberto Romero
2003-05-01 8:32 ` mike wakerly
2003-05-01 8:42 ` Tony Clark [this message]
2003-05-01 12:56 ` Daniel Armyr
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=200305011042.24128.tclark@telia.com \
--to=tclark@telia.com \
--cc=gentoo-dev@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