Summary: | media-video/mplayer-1.0_rc4_p20110322-r1 - fails on extracting fonts, though they are not requested | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | avx <idevelop> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED CANTFIX | ||
Severity: | normal | CC: | floppym |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://forums.gentoo.org/viewtopic-t-895248-highlight-.html | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | environment |
Description
avx
2011-10-24 15:58:09 UTC
Created attachment 290727 [details]
environment
Your environment file has an empty USE variable, which is very odd: declare -x USE="" Are you overriding USE in /etc/portage/bashrc, or /etc/portage/env/media-video/mplayer*? (In reply to comment #2) > Your environment file has an empty USE variable, which is very odd: > > declare -x USE="" > > Are you overriding USE in /etc/portage/bashrc, or > /etc/portage/env/media-video/mplayer*? Let me start with, you sir are my personal hero - at least for the day :) In fact, I played with /etc/portage/package.env & the corresponding /etc/portage/env/media-video/mplayer. But I've got > #media-video/mplayer media-video/mplayer in package.env and thought this would comment it out. IIRC in package.env one shall define a config to read, thus I thought adding a # would comment it. Either this is a bug, something in portage changed in the meantime or I misunderstood the manpage. Anyway, I just deleted the file in question and it works again. Since I guess this was my fault, I'm setting this to resolved->cantfix (change if it's a bug). Thanks again :) (In reply to comment #3) /etc/portage/env is sort of confusing since it contains files for 2 separate features: 1. /etc/portage/env/category/pkg files are processed as per-package bashrc files. 2. /etc/portage/env/* files are referenced by the /etc/portage/package.env file to provide per-package make.conf overrides. #1 only affects ebuild(1), so it is buggy to use it for environment variables. #2 affects both ebuild(1) and emerge(1), and is the preferred method for setting environment variables. Hope that clears it up. Ah, ok, then it was just a misunderstanding. I thought I could name the file whatever I want and thus chose the same scheme I'll use for my package.{unmask,use}-dirs, so it's more logical and organized to me. Something like: /etc/portage/env/cat/app/name.rc and /etc/portage/env/cat/app/name.make would be more logical and less confusing, imho. Alternatively, if it doesn't have a #! in it, it should be treated as make.conf overrides... Thanks for clarification. |