| Summary: | perl upgrade should mark dependents for rebuild | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Roy Marples <roy> |
| Component: | [OLD] Core system | Assignee: | Gentoo Perl team <perl> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | tove |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Roy Marples
2010-03-09 07:25:53 UTC
(In reply to comment #0) > checking for XML::Parser... configure: error: XML::Parser perl module is > required for intltool > > !!! Please attach the following file when seeking support: > !!! /var/tmp/portage/dev-util/intltool-0.41.0/work/intltool-0.41.0/config.log > * ERROR: dev-util/intltool-0.41.0 failed: > * econf failed > You may have update Perl recently from 5.8.8 to 5.10. Try running 'perl-cleaner --all' and see if your issue disappears. (In reply to comment #1) > (In reply to comment #0) > > checking for XML::Parser... configure: error: XML::Parser perl module is > > required for intltool > > > > !!! Please attach the following file when seeking support: > > !!! /var/tmp/portage/dev-util/intltool-0.41.0/work/intltool-0.41.0/config.log > > * ERROR: dev-util/intltool-0.41.0 failed: > > * econf failed > > > You may have update Perl recently from 5.8.8 to 5.10. Try running 'perl-cleaner > --all' and see if your issue disappears. > P.S. XML::Parser is installed already on a default system. I shouldn't have to do this, portage should be able to handle it for me. (In reply to comment #3) > I shouldn't have to do this, portage should be able to handle it for me. How would you do it? Already have an idea? Well, pkgsrc (NetBSD package manager) handles it nicely by marking dependants to rebuild. This works because the list and order of packages is evaluated after each package merge. I know that portage doesn't work like that, but maybe it could re-calculate things when a package marked a such is built? The downside of the pkgsrc approach is that it's applied across the board, so dependants get rebuild even when they don't technically need to. On the other hand, this saves having news items saying "ABI changed but .so version did not so you need to rebuild mesa, xorg and your drivers". I, as a user, have to read, understand and action that (quite a lot of late it seems). With pkgsrc I don't have to - burns CPU, but saves me time thus happier. Duplicate of Bug 192319. And good luck with that :P I would argue that a basic requirement of a package manager is to handle upgrades like this cleanly and easily. The answer to this requirement should not be "good luck with that". Well, I for one absolutely don't want the described BSD behaviour (useless recompiles forced on me for no good reason). Anyway, this bug is a duplicate, so ... the discussion should move to the relevant bug. And good luck with that means just that - good luck will be needed as with anything that's in hands of PMS folks :P *** This bug has been marked as a duplicate of bug 192319 *** |
