1 |
Jürgen Schinker posted |
2 |
<49586.10.10.10.10.1144392073.squirrel@×××××××××××××××××××.net>, excerpted |
3 |
below, on Fri, 07 Apr 2006 08:41:13 +0200: |
4 |
|
5 |
> yeah i emerge xorg-x11 and it pulls font-adobe-75dpi and than stops with |
6 |
> an error..... |
7 |
> |
8 |
> its hard to reproduce coz i have to uninstall xorg-6.8... |
9 |
> |
10 |
> every time and reinstall it so my system will be blocked a long time |
11 |
|
12 |
It appears you may be unaware of one of my favorite not-well-enough-known |
13 |
portage features. Try reading up on portage FEATURES=buildpkg. (There's |
14 |
a bit on it in the Gentoo Handbook, and there's also info about it in the |
15 |
make.conf manpage and in make.conf.example. It's also googleable.) |
16 |
|
17 |
Basically, what FEATURES=buildpkg does is tell portage to build a binary |
18 |
package every time it merges something. It then actually does the merge to |
19 |
the live system from the binary package, thereby testing the package it |
20 |
just created so you know right away if it fails for whatever reason. |
21 |
|
22 |
With this set, you'll eventually have binary packages for everything on |
23 |
your system, and any upgrade will build a binary package for it as well. |
24 |
That way, if the upgrade doesn't go as expected, you can quickly remerge |
25 |
the old version from its binary package (using emerge -K or -k, see man |
26 |
emerge), without having to wait for it to recompile again. Likewise, once |
27 |
the initial merge of a package version is accomplished and the binary |
28 |
package built, it's relatively easy to switch between the old and the new |
29 |
version, by just merging the version you want using the -K switch so |
30 |
portage uses the package rather than trying to remerge from source. |
31 |
|
32 |
The space required to store one copy of all the binary packages for an |
33 |
entire system will run 1-2 gig, typically. Because you'll want to keep |
34 |
old versions around until you know the new ones are working right, and to |
35 |
prevent having to weed out the old ones too frequently, figure four gig or |
36 |
so. |
37 |
|
38 |
Alternatively, or to create a binpkg out of something already merged to |
39 |
your system, there's the quickpkg tool. For this situation, since you |
40 |
won't have built xorg-6.8 with FEATURES=buildpkg yet, the binary won't be |
41 |
available yet, so use quickpkg to create the binary package out of what's |
42 |
already on your system. That'll give you an xorg-6.8 binary package, so |
43 |
you can unmerge it and try merging 7.0 again. Once you've done your |
44 |
troubleshooting, you can remerge 6.8 from the binary package you just |
45 |
created, without waiting for it to recompile. It's still a hassle, but |
46 |
significantly /less/ of one than having to wait for 6.8 to complete a full |
47 |
recompile cycle too! |
48 |
|
49 |
... |
50 |
|
51 |
FWIW, font-adobe-75dpi is pulled in as a dependency only because it's used |
52 |
by one of the xconfig applets (I believe I got that from the changelog). |
53 |
If you don't plan to run that, say you already have a working config, you |
54 |
won't need that specific package. You'll likely want either that or the |
55 |
100dpi version, but either will do and it's likely you could do without |
56 |
both if necessary. |
57 |
|
58 |
Still, without the specific error it's hard to say whether it's directly a |
59 |
font-adobe-75dpi issue, which you can avoid by simply package.provided-ing |
60 |
that package, or a problem with the font utils, as suggested by others, in |
61 |
which case it's likely you'll have problems with other fonts as well, so |
62 |
avoiding this package won't do any good even if it's /not/ specifically |
63 |
needed other than for something you won't be running anyway. |
64 |
|
65 |
-- |
66 |
Duncan - List replies preferred. No HTML msgs. |
67 |
"Every nonfree program has a lord, a master -- |
68 |
and if you use the program, he is your master." Richard Stallman in |
69 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
70 |
|
71 |
|
72 |
-- |
73 |
gentoo-amd64@g.o mailing list |