From: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] First Portage Hick-up, Chokes on Java
Date: Fri, 3 Oct 2008 04:53:14 +0200 [thread overview]
Message-ID: <200810030453.15274.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0810030155570.21240@strider.Belkin>
On Freitag 03 Oktober 2008, 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_Devel
>oper * (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.
> *
> * If emerge fails because of a md5sum error it is possible that Sun
> * has again changed the upstream release, try downloading the file
> * again or a newer revision if available. Otherwise report this to
> * http://bugs.gentoo.org/67266 and we will make a new revision.
> * Fetch failed for 'dev-java/java-sdk-docs-1.6.0-r1'
>
> * Messages for package dev-java/java-sdk-docs-1.6.0-r1:
>
> * Fetch failed for 'dev-java/java-sdk-docs-1.6.0-r1
>
> So, I downloaded the file, renamed it and put it where it told me to.
really? and did you rename it?
> Then I found http://gentoo-wiki.com/HOWTO_Installing_3rd_Party_Ebuilds and
> I am trying to follow that.
why?
>
> I added PORTDIR_OVERLAY="/usr/local/portage /usr/portage/distfiles" to
> /etc/make.conf The first because the wki said to, and the second because
> that's where emerge's message told me to put the file I downloaded from
> Sun.
again, why? all you need to do is downloading the file and put it into
/usr/portage/distfiles. And don't add that to make.conf as an overlay
directory. it is just wrong.
> OK, so I created it. Now, that is where emerge told me to put the file,
> but the fact that gentoo did not even create that directory gives me
> pause.
why should emerge create a directory that it doesn't even need?
>
> Bottom line: I am being told I need this dependency, and I am not sure
> how to proceed in creating my own Ebuild to install it.
you don't need to create the ebuild. It is a dependency/file needed. The
ebuild is already there.
>
> Am I even in the right ballpark here?
I am afraid: no
next prev parent reply other threads:[~2008-10-03 2:54 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 ` Volker Armin Hemmann [this message]
2008-11-04 14:16 ` [gentoo-user] " Jorge Peixoto de Morais Neto
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=200810030453.15274.volker.armin.hemmann@tu-clausthal.de \
--to=volker.armin.hemmann@tu-clausthal.de \
--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