URN Logo
UNIX Resources » Linux » Linux Forum » Gentoo Help » Page.65 » No X whatsoever. accomplishEver.
announcement The content of this page is collected from Linux Forum, All copyrights and other associated rights are reserved by the original authors of the articles.
Resources
China Linux Forum(finished)
Linux Forum(finished)
FreeBSD China(finished)
linuxforum.com
  LinuxForum General Chat
  Linux Advocacy
  LinuxForum Polls
  Introductions
  Linux Kernel Support
  Patch Management
  Development Release
  Linux Programming
  Linux Security
  Linux Software
  Linux Hardware Problems
    Linux Video Problems
    Linux Sound Problems
  Linux Networking Support
  Linux Printing Support
  Linux Human Interface Devices Support
  Linux Data Storage Support
  Linux Applications Support
  Linux Installation Support
  Linux Laptops Support
  Linux Motherboard, Chipsets, CPU, Memory
  Miscellaneous
  Debian Linux Support
  Ubuntu Linux Support
  LiveCD Discussions
  Gentoo Linux Support
  Mandrake Linux Support
  Redhat / Fedora Linux Support
  Slackware Linux Support
  SuSE Linux Support
  CentOS Linux Support
  Linux Web Servers
  Linux DNS Servers
  Linux Database Servers
  Linux Email Servers
  Linux FTP Servers
  Linux Squid Proxy Server
  Linux Samba Help
  Linux cPanel Help
  Linux Ensim Help
  Linux Plesk Help
  Linux Webmin / Usermin Help
  Qmail Toaster Help
  Linux Games
  Windows Game Emulation
  Linux Discussions
  General Linux Discussions
  Red Hat Linux Discussions
  More Red Hat Linux Discussions
  Mandrake Linux Discussions
  Slackware Linux Discussions
  SuSE Linux Discussions
  Debian Discussions
  Samba Help
  Linux Security
  Linux Networking
  Gentoo Help
  Operating System Rant Forum
  Hardware Rants
   
No X whatsoever. accomplishEver.
Subject: No X whatsoever. accomplishEver.
Author: Bjørn Halvor Bergtun    Posted: 2003-10-21 15:12:58    Length: 414 byte(s)
[Original] [Print] [Top]
How can I make sure that X wount be installed on my server? I thought
that a USE="-X -gnome -gtk -gtk2 -kde -qt" should cover it, but a quick
emerge -pv mplayer still insists on installing xfree and a bunch of
other X-related stuff. Are there other USE-flags I should use, or are
there different ways to accomplish this?

--
mvh / Regards
Bjørn Halvor Bergtun

[Original] [Print] [Top]
Subject: No X whatsoever. accomplishEver.
Author: PipHans    Posted: 2003-10-21 15:18:39    Length: 1,249 byte(s)
[Original] [Print] [Top]
Bjørn Halvor Bergtun wrote:
QUOTE
How can I make sure that X wount be installed on my server? I thought
that a USE="-X -gnome -gtk -gtk2 -kde -qt" should cover it, but a
quick emerge -pv mplayer still insists on installing xfree and a
bunch of other X-related stuff. Are there other USE-flags I should
use, or are there different ways to accomplish this?

Afaik you are under the mercy of the ebuild...If it explicitly dictates X as
a dependancy, then you will get X installed...In theory a correct approach
to the issue, but in real life you _will_ come across lousy ebuilds and
stuff.

Allways inspect your emerge with a "emerge -p [whatever]" in order to
inspect things.

If you are absolutely sure that an ebuild is referencing a rediculous
dependancy you could allways edit the ebuild file yourself..and thus avoid
things...but be aware that this approach is only for those who really
understand the complications of such actions :)

--
Pip

[Original] [Print] [Top]
Subject: No X whatsoever. accomplishEver.
Author: Jon Portnoy    Posted: 2003-10-21 15:25:04    Length: 1,893 byte(s)
[Original] [Print] [Top]
On 2003-10-21, PipHans [piphans@hotmail.com] wrote:
QUOTE
Bjørn Halvor Bergtun wrote:
How can I make sure that X wount be installed on my server? I thought
that a USE="-X -gnome -gtk -gtk2 -kde -qt" should cover it, but a
quick emerge -pv mplayer still insists on installing xfree and a
bunch of other X-related stuff. Are there other USE-flags I should
use, or are there different ways to accomplish this?

Afaik you are under the mercy of the ebuild...If it explicitly dictates X as
a dependancy, then you will get X installed...In theory a correct approach
to the issue, but in real life you _will_ come across lousy ebuilds and
stuff.

Allways inspect your emerge with a "emerge -p [whatever]" in order to
inspect things.

If you are absolutely sure that an ebuild is referencing a rediculous
dependancy you could allways edit the ebuild file yourself..and thus avoid
things...but be aware that this approach is only for those who really
understand the complications of such actions :)


The mplayer ebuild actually doesn't explicitly depend on X. However, it
depends on lots of stuff which may have dependencies on X.

Hint: the tcltk USE flag will pull in tk which will pull in X. There are
probably others. Your best bet for USE flags for a minimalist
configuration is to do:

USE="-* useflag1 useflag2 useflag3..."

--
Jon Portnoy
avenj/irc.freenode.net #gentoo, irc.oftc.net #cola
Opinions expressed are my own, not those of Gentoo Linux or any
other entity I am associated with unless stated otherwise.

[Original] [Print] [Top]
Subject: No X whatsoever. accomplishEver.
Author: Bjørn Halvor Bergtun    Posted: 2003-10-21 15:51:08    Length: 2,013 byte(s)
[Original] [Print] [Top]
Sorry for the subject line. Don't know how I accomplished that... (Pun
intended.)

PipHans wrote:
QUOTE
Afaik you are under the mercy of the ebuild...If it explicitly
dictates X as a dependancy, then you will get X installed...In theory
a correct approach to the issue, but in real life you _will_ come
across lousy ebuilds and stuff.

OK. Thanks for clarifying that for me. I was under the impression that
if I spesified no X, then it wouldn't install X, but alas. Would masking
known "trouble-packages" help? (E.g. the package invoked by tcltk/tk.
Thanks to Portnoy for pointing that out.)

QUOTE
Allways inspect your emerge with a "emerge -p [whatever]" in order to
inspect things.

I allways do, but I would hate to get X installed by mistake only
because I forgot to check one little unimportant package. Does the
emerge-tool have a rollback-feature for such cases? -As in undoing all
actions as a ressult of the latest emerge?

QUOTE
If you are absolutely sure that an ebuild is referencing a rediculous
dependancy you could allways edit the ebuild file yourself..and thus
avoid things...but be aware that this approach is only for those who
really understand the complications of such actions :)

:P
It's only a messing-around-for-fun-test-server, so I can afford it.

--
mvh / Regards

[Original] [Print] [Top]
Subject: No X whatsoever. accomplishEver.
Author: Jason    Posted: 2003-10-21 20:26:07    Length: 2,311 byte(s)
[Original] [Print] [Top]
There is no roll back feature that I know of, however, you can check
through the emerge logs to see what order the packages were emerged in
and then run "emerge unmerge [package]" manually for each package you
want to remove.

An easy way to check the emerge logs is to install the package
"genlop" (it was featured in this week's newsletter).  Once it's
installed you can run the command "genlop -ul" and it will display a
complete record of the date, time, and version of every package you've
ever installed/uninstalled.

On Tue, 21 Oct 2003 22:51:08 +0200, "Bjørn Halvor Bergtun"
[ask-me@online.nospam.invalid] wrote:

QUOTE
Sorry for the subject line. Don't know how I accomplished that... (Pun
intended.)

PipHans wrote:
Afaik you are under the mercy of the ebuild...If it explicitly
dictates X as a dependancy, then you will get X installed...In theory
a correct approach to the issue, but in real life you _will_ come
across lousy ebuilds and stuff.

OK. Thanks for clarifying that for me. I was under the impression that
if I spesified no X, then it wouldn't install X, but alas. Would masking
known "trouble-packages" help? (E.g. the package invoked by tcltk/tk.
Thanks to Portnoy for pointing that out.)

Allways inspect your emerge with a "emerge -p [whatever]" in order to
inspect things.

I allways do, but I would hate to get X installed by mistake only
because I forgot to check one little unimportant package. Does the
emerge-tool have a rollback-feature for such cases? -As in undoing all
actions as a ressult of the latest emerge?

If you are absolutely sure that an ebuild is referencing a rediculous
dependancy you could allways edit the ebuild file yourself..and thus
avoid things...but be aware that this approach is only for those who
really understand the complications of such actions :)

:P
It's only a messing-around-for-fun-test-server, so I can afford it.


[Original] [Print] [Top]
« Previous thread
New to Gentoo
Gentoo Help
Page. 65
Next thread »
gentoo on 386
     

Copyright © 2007 UNIX Resources Network, All Rights Reserved.      About URN | Privacy & Legal | Help | Contact us
Powered by FreeBSD    webmaster: webmaster@unixresources.net
This page created on 2007-08-01 13:20:27, cost 0.027174949645996 ms.