-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Neil Bothwick wrote:
| On Thu, 5 Jan 2006 11:10:38 +0000, Tom Martin wrote:
|
|>> To the portage developers, how could this be handled? Perhaps emerge
|>> could somehow figure out the reason for such a conflict, and then
|>> automatically unmerge the original package?
|
|> Not really a question to the portage developers -- just unmerge
|> openmotif (the blocker) and continue as normal.
|
| If would be nice is portage had a means for developers to handle these
| types of conflicts in the ebuild. A similar thing happened recently with
| xpdf/poppler, it happened with some FTP servers and the ftp-base package
| not long ago. I realise it is not possible to handle all conflicts, but
| with some instances, like this one, the conflict is expected. even if
| there were just a means to print a message if a package hits a block,
| something like
|
| if_blocked_by('openmotif')
| ewarn "You must unmerge openmotif before proceeding"
|
It would be icky to have to specify blocker logic/messages like that. There's
actually an open bug specifically about this issue:
http://bugs.gentoo.org/show_bug.cgi?id=79606
Basically, the problem lies in the fact that portage unmerges the previous
version _after_ the new version has been merged into place. One possible
solution would be to have a special feature that, when enabled, allows portage
to automatically unmerge an old version _before_ the new one is installed (with
protection against unmerging system packages of course).
Zac
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDvcR8/ejvha5XGaMRAnICAKDyA6xKtGb6mZXxS/mciU91Xvsz8QCeKidL
WRXlWMkvZ7plI2fNPlxO0TA=
=VAP2
-----END PGP SIGNATURE-----
--
[email protected] mailing list
