| 1 |
On Thu, Oct 2, 2008 at 11:08 PM, boslists@×××××.com <boslists@×××××.com> wrote: |
| 2 |
> My first install of Gentoo, and I'm pleased by how far I've progressed on my |
| 3 |
> own, not being a programmer or computer person, but I'm a bit wary of |
| 4 |
> proceeding further without advice. |
| 5 |
> |
| 6 |
> I was trying to emerge some several files which had a dependency on |
| 7 |
> java-sdk-docs. Below is the message from emerge. More information will |
| 8 |
> follow. |
| 9 |
> |
| 10 |
> !!! dev-java/java-sdk-docs-1.6.0-r1 has fetch restriction turned on. |
| 11 |
> !!! This probably means that this ebuild's files must be downloaded |
| 12 |
> !!! manually. See the comments in the ebuild for more information. |
| 13 |
> |
| 14 |
> * Please download jdk-6-doc.zip from |
| 15 |
> * |
| 16 |
> https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/ViewProductDetail-Start?ProductRef=jdk-6-doc-oth-JPR@CDS-CDS_Developer |
| 17 |
> * (select English and agree to the licence) and place it in |
| 18 |
> /usr/portage/distfiles named as |
| 19 |
> * jdk-6-doc-r1.zip. Notice the r1. Because Sun changes the doc zip file |
| 20 |
> * without changing the filename, we have to resort to renaming to keep |
| 21 |
> * the md5sum verification working for existing and new downloads. |
| 22 |
> * |
| 23 |
[snip] |
| 24 |
> So, I downloaded the file, renamed it and put it where it told me to. |
| 25 |
Fine, you should indeed have downloaded the jdk-6-doc.zip file and put |
| 26 |
it (with the correct name) in portage's DISTDIR (DISTDIR is, by |
| 27 |
default, /usr/portage/distfiles). |
| 28 |
|
| 29 |
> Then I |
| 30 |
> found http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds and I am |
| 31 |
> trying to follow that. |
| 32 |
No no no, this is *not* a third party ebuild. It is an official Gentoo |
| 33 |
ebuild, that unfortunately needs you to manually fetch this |
| 34 |
jdk-6-doc.zip file. This is *not* a third party ebuild. |
| 35 |
Rest assured that manually fetching files is, fortunately, very uncommon. |
| 36 |
> |
| 37 |
> I added PORTDIR_OVERLAY="/usr/local/portage /usr/portage/distfiles" to |
| 38 |
> /etc/make.conf |
| 39 |
No. Undo this. /usr/porage/distfiles is *not* a portage overlay and |
| 40 |
*must not* be in PORTDIR_OVERLAY. Remove it. |
| 41 |
/usr/local/portage is a common location for putting a gentoo overlay, |
| 42 |
but since you probably don't have an overlay (many, if not most, |
| 43 |
people don't need an overlay), don't care about /usr/local/portage. |
| 44 |
Remove the directory name from PORTDIR_OVERLAY and them remove the |
| 45 |
directory /usr/local/portage itself with the command rmdir --verbose |
| 46 |
/usr/local/portage. |
| 47 |
> I then added FEATURES="collision-protect ccache parallel-fetch" to |
| 48 |
> /etc/male.conf for safety, even though I have no idea what it does. |
| 49 |
Don't add features without a basic knowledge of what they mean. |
| 50 |
In fact, this is a big lesson: |
| 51 |
|
| 52 |
*Don't mess with your system without a basic knowledge of what you are doing* |
| 53 |
I did it more than once and broke my system more than once. Do not |
| 54 |
repeat the same mistake. |
| 55 |
|
| 56 |
Look /etc/make.conf.example for a brief explanation of what which |
| 57 |
feature means. I personally use parallell-fetch. It speeds up emerging |
| 58 |
multiple packages, because it enables Portage to download one package |
| 59 |
source in the background while it emerges another package in the |
| 60 |
foreground. In fact, I don't know why this isn't enabled by default. |
| 61 |
I don't use ccache, because AFAIK it speeds up compilation at the |
| 62 |
expense of consuming tons of disk space. I am satisfied with my |
| 63 |
compile speed (I use lightweight programs, and these tend to compile |
| 64 |
quickly), but I want my disk to have a lot of free space so that disk |
| 65 |
access is faster. |
| 66 |
collision-protect seems nice, but I don't know about its drawbacks (if |
| 67 |
any), and since it seems not to be default and I don't have good |
| 68 |
knowledge of it, I didn't change the default. |
| 69 |
|
| 70 |
[snip] |
| 71 |
> /usr/local/portage did not exist. |
| 72 |
> OK, so I created it. Now, that is where emerge told me to put the file |
| 73 |
No, it told you to put the file in /usr/portage/distfiles. |
| 74 |
[snip] |
| 75 |
> I am not sure how to proceed in creating my own Ebuild to install it. |
| 76 |
You don't need to, and very probably should not. |
| 77 |
> Am I even in the right ballpark here? |
| 78 |
No. *All* you had to do was fetch the required file and put it, with |
| 79 |
the specified name, in Portage's DISTDIR, which is |
| 80 |
/usr/portage/distfiles by default. |
| 81 |
Everything else you did without knowing what you were doing should |
| 82 |
probably be undone, to return the system to its safe default |
| 83 |
configuration. |
| 84 |
|
| 85 |
> Thanks, |
| 86 |
> Bo Grimes |
| 87 |
You're welcome |
| 88 |
|
| 89 |
-- |
| 90 |
Software is like sex: it is better when it is free - Linus Torvalds |
Archives