Summary: | gst-plugin weirdness (10.21-r1) -- won't emerge. File collisions & missing libraries | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Waldo <VValdo> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | leio, ssuominen |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Waldo
2008-12-28 22:32:44 UTC
Scratch that. For some reason, gstreamer and gst-plugins-base (along with all the gst-plugins) were in /etc/package.unmask. They are what broke this, and rebuilding the ~amd64 versions seems to be fixing the problem. W Reopening and closing with correct resolution and notifying Samuli via CC what his experimentation is causing. I am inclined to kill those monolithic revision from the tree soon because there has been no reasonable explanation given why it makes sense to introduce monolithic plugin packages (In reply to comment #3) > and closing with correct resolution and notifying Samuli via CC what his > experimentation is causing. Is causing? package.mask is there for an reason, seems pebcak. > I am inclined to kill those monolithic revision from the tree soon because > there has been no reasonable explanation given why it makes sense to introduce > monolithic plugin packages > USE deps in stable tree, Portage 2.2 with better block handling to smooth the transition, easier maintaintance, easier to add new plugins (see ChangeLog gst-plugins-bad for example), dropped libtool files & static libs as unnecessary, as such build (link) times doesn't get much longer. Besides we are already building the whole sets (internal plugins as well) over and over again (just see what media-plugins/gst-plugins-cdparanoia for example does). So as for perfomance, install time.. But please do kill them, if you want. They have been package.masked from the beginning, as i'm far from done with those. That's what the package.mask is for, for packages not ready for public consumption.. We can discuss the pros and cons soon as I'm in IRC again? |