Thomas Kirchner <[EMAIL PROTECTED]> writes:

> * On Feb  3 13:37, Harry Putnam ([email protected]) wrote:
>> But as I comment out the entries there are always more that turn up
>> when I run emerge xvidtune again.  I've commented about 8 so
>> far.... but haven't done any real installing just seeing where this
>> goes and need some coaching from someone who better understands what I
>> might be getting into.
>
> You shouldn't be editing any files in /usr/portage yourself - they'll 
> just be overwritten on your next emerge sync.  Instead, put 
> "package-category/name" (without the quotes) into 
> /etc/portage/package.unmask .  (If that file doesn't exist, create it.)

That doesn't appear to have the disired effect here...

  cat /etc/portage/package.unmask
  x11-apps/xvidtune
===================================
  root # emerge -vp xvidtune
  
  These are the packages that I would merge, in order:
    Calculating dependencies -
  !!! All ebuilds that could satisfy "x11-libs/libXxf86vm" have been masked.
  !!! One of the following masked packages is required to complete your request:
  - x11-libs/libXxf86vm-1.0.0 (masked by: package.mask)
  # Donnie Berkholz <[EMAIL PROTECTED]> (07 Aug 2005)
  # Modularized X, upstream release candidates
  [...]

Or are you saying I need to list ever dependance in there too?
Its a very long list.  I got as high as 12 and was still getting that
message with yet another dependancy.

What can I do to automate or batch some of this.  Or is there some way
to just install xvidtune and get on with it.  I had it installed in a
previous install with none of this coming up less than 2 mnths ago.

  root # equery depends  x11-apps/xvidtune
   [ Searching for packages depending on x11-apps/xvidtune... ]

Shows nothing...

-- 
[email protected] mailing list

Reply via email to