| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Neil Bothwick wrote: |
| 5 |
| On Thu, 5 Jan 2006 11:10:38 +0000, Tom Martin wrote: |
| 6 |
| |
| 7 |
|>> To the portage developers, how could this be handled? Perhaps emerge |
| 8 |
|>> could somehow figure out the reason for such a conflict, and then |
| 9 |
|>> automatically unmerge the original package? |
| 10 |
| |
| 11 |
|> Not really a question to the portage developers -- just unmerge |
| 12 |
|> openmotif (the blocker) and continue as normal. |
| 13 |
| |
| 14 |
| If would be nice is portage had a means for developers to handle these |
| 15 |
| types of conflicts in the ebuild. A similar thing happened recently with |
| 16 |
| xpdf/poppler, it happened with some FTP servers and the ftp-base package |
| 17 |
| not long ago. I realise it is not possible to handle all conflicts, but |
| 18 |
| with some instances, like this one, the conflict is expected. even if |
| 19 |
| there were just a means to print a message if a package hits a block, |
| 20 |
| something like |
| 21 |
| |
| 22 |
| if_blocked_by('openmotif') |
| 23 |
| ewarn "You must unmerge openmotif before proceeding" |
| 24 |
| |
| 25 |
|
| 26 |
It would be icky to have to specify blocker logic/messages like that. There's actually an open bug specifically about this issue: |
| 27 |
|
| 28 |
http://bugs.gentoo.org/show_bug.cgi?id=79606 |
| 29 |
|
| 30 |
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). |
| 31 |
|
| 32 |
Zac |
| 33 |
-----BEGIN PGP SIGNATURE----- |
| 34 |
Version: GnuPG v1.4.2 (GNU/Linux) |
| 35 |
|
| 36 |
iD8DBQFDvcR8/ejvha5XGaMRAnICAKDyA6xKtGb6mZXxS/mciU91Xvsz8QCeKidL |
| 37 |
WRXlWMkvZ7plI2fNPlxO0TA= |
| 38 |
=VAP2 |
| 39 |
-----END PGP SIGNATURE----- |
| 40 |
-- |
| 41 |
gentoo-user@g.o mailing list |
Archives