From: "Jorge Peixoto de Morais Neto" <please.no.spam.here@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] First Portage Hick-up, Chokes on Java
Date: Tue, 4 Nov 2008 12:16:30 -0200 [thread overview]
Message-ID: <38af3d670811040616r77307a6cxb7237ac4618353cd@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810030155570.21240@strider.Belkin>
On Thu, Oct 2, 2008 at 11:08 PM, boslists@gmail.com <boslists@gmail.com> wrote:
> My first install of Gentoo, and I'm pleased by how far I've progressed on my
> own, not being a programmer or computer person, but I'm a bit wary of
> proceeding further without advice.
>
> I was trying to emerge some several files which had a dependency on
> java-sdk-docs. Below is the message from emerge. More information will
> follow.
>
> !!! dev-java/java-sdk-docs-1.6.0-r1 has fetch restriction turned on.
> !!! This probably means that this ebuild's files must be downloaded
> !!! manually. See the comments in the ebuild for more information.
>
> * Please download jdk-6-doc.zip from
> *
> 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
> * (select English and agree to the licence) and place it in
> /usr/portage/distfiles named as
> * jdk-6-doc-r1.zip. Notice the r1. Because Sun changes the doc zip file
> * without changing the filename, we have to resort to renaming to keep
> * the md5sum verification working for existing and new downloads.
> *
[snip]
> So, I downloaded the file, renamed it and put it where it told me to.
Fine, you should indeed have downloaded the jdk-6-doc.zip file and put
it (with the correct name) in portage's DISTDIR (DISTDIR is, by
default, /usr/portage/distfiles).
> Then I
> found http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds and I am
> trying to follow that.
No no no, this is *not* a third party ebuild. It is an official Gentoo
ebuild, that unfortunately needs you to manually fetch this
jdk-6-doc.zip file. This is *not* a third party ebuild.
Rest assured that manually fetching files is, fortunately, very uncommon.
>
> I added PORTDIR_OVERLAY="/usr/local/portage /usr/portage/distfiles" to
> /etc/make.conf
No. Undo this. /usr/porage/distfiles is *not* a portage overlay and
*must not* be in PORTDIR_OVERLAY. Remove it.
/usr/local/portage is a common location for putting a gentoo overlay,
but since you probably don't have an overlay (many, if not most,
people don't need an overlay), don't care about /usr/local/portage.
Remove the directory name from PORTDIR_OVERLAY and them remove the
directory /usr/local/portage itself with the command rmdir --verbose
/usr/local/portage.
> I then added FEATURES="collision-protect ccache parallel-fetch" to
> /etc/male.conf for safety, even though I have no idea what it does.
Don't add features without a basic knowledge of what they mean.
In fact, this is a big lesson:
*Don't mess with your system without a basic knowledge of what you are doing*
I did it more than once and broke my system more than once. Do not
repeat the same mistake.
Look /etc/make.conf.example for a brief explanation of what which
feature means. I personally use parallell-fetch. It speeds up emerging
multiple packages, because it enables Portage to download one package
source in the background while it emerges another package in the
foreground. In fact, I don't know why this isn't enabled by default.
I don't use ccache, because AFAIK it speeds up compilation at the
expense of consuming tons of disk space. I am satisfied with my
compile speed (I use lightweight programs, and these tend to compile
quickly), but I want my disk to have a lot of free space so that disk
access is faster.
collision-protect seems nice, but I don't know about its drawbacks (if
any), and since it seems not to be default and I don't have good
knowledge of it, I didn't change the default.
[snip]
> /usr/local/portage did not exist.
> OK, so I created it. Now, that is where emerge told me to put the file
No, it told you to put the file in /usr/portage/distfiles.
[snip]
> I am not sure how to proceed in creating my own Ebuild to install it.
You don't need to, and very probably should not.
> Am I even in the right ballpark here?
No. *All* you had to do was fetch the required file and put it, with
the specified name, in Portage's DISTDIR, which is
/usr/portage/distfiles by default.
Everything else you did without knowing what you were doing should
probably be undone, to return the system to its safe default
configuration.
> Thanks,
> Bo Grimes
You're welcome
--
Software is like sex: it is better when it is free - Linus Torvalds
next prev parent reply other threads:[~2008-11-04 14:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 2:08 [gentoo-user] First Portage Hick-up, Chokes on Java boslists
2008-10-03 2:30 ` Dale
2008-10-03 2:54 ` boslists
2008-10-03 2:49 ` [gentoo-user] " »Q«
2008-10-03 2:58 ` boslists
2008-10-04 11:22 ` b.n.
2008-10-04 11:54 ` boslists
2008-10-04 16:48 ` Dale
2008-10-03 2:53 ` [gentoo-user] " Volker Armin Hemmann
2008-11-04 14:16 ` Jorge Peixoto de Morais Neto [this message]
2008-11-04 15:23 ` Alan McKinnon
2008-11-04 17:56 ` Jorge Peixoto de Morais Neto
2008-11-04 18:26 ` Alan McKinnon
2008-11-04 18:47 ` Jorge Peixoto de Morais Neto
2008-11-05 15:16 ` Willie Wong
2008-11-05 15:27 ` Jorge Peixoto de Morais Neto
2008-11-06 15:24 ` Joshua Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38af3d670811040616r77307a6cxb7237ac4618353cd@mail.gmail.com \
--to=please.no.spam.here@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox