public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <dalek@exceedtech.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Packages from overlays
Date: Sat, 13 Jan 2007 00:28:14 -0600	[thread overview]
Message-ID: <45A87BFE.5000300@exceedtech.net> (raw)
In-Reply-To: <8cd1ed20701122027s6e0bce07qeae5119428cddcc@mail.gmail.com>

Kent Fredric wrote:
> On 1/13/07, Dale <dalek@exceedtech.net> wrote:
>> You may want to reconsider this.  I have googleearth installed here and
>> it doesn't get along well with portage and it's digest checking.  Of
>> course, it doesn't like my dial-up either.  LOL
>
> It would appear google has updated their package without changing the
> name, and portage has not been notified of this change. If you want it
> to work, delete the digest file for it in
> ${PORTAGE_DIR}/x11-misc/googleearth/files/digest-googleearth-4_beta
> and then re-generate it with
> ebuild ${PORTAGE_DIR}/x11-misc/googleearth/googleearth-4_beta digest
>
> and that should fix you up. I found it still compiles and runs fine
> *shrugs*
>

True, you hit the problem right on the head.  That is exactly what they
do.  But what I had noticed is that they change that thing a lot.  Since
I am on a really slow dial-up here, I check for updates, sync, every
couple days or so.  While I know that it comes from Google and I don't
question the tarball from a security point of view, portage still
complains about it each time and deletes it for me, since it thinks it
is a security problem.  That would normally be a great idea but then I
have to download it again, which takes a little over two hours for me.
I get about 10Mbs a hour here.  < goes to have a good cry >

Plus, it is a pain in the butt to have to manually do the digest thing
every time I sync up too.  My solution was to remove it from the world
file, since portage had already deleted the tarball and I didn't want to
download it again to do a oneshot install.  Now the only drawback is
that --depclean -p tells me it is not needed since it is not in the
world file and is not a dependancy.  I do that manually anyways so it
doesn't matter.

I'm no guru but if he wants it out of overlay, he may want to emerge it
as a oneshot at least.  Then just check for updates on occasion.  I had
to use the --digest option too when I installed it.  That way it assumes
it is OK and doesnt' check it.

Hope that makes sense.  Maybe . . . .   LOL

Dale

:-)  :-)  :-)

-- 
www.myspace.com/dalek1967


-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2007-01-13  6:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-13  0:49 [gentoo-user] Packages from overlays Willie Wong
2007-01-13  4:15 ` Dale
2007-01-13  4:27   ` Kent Fredric
2007-01-13  6:28     ` Dale [this message]
2007-01-13  6:47       ` Bo Ørsted Andresen
2007-01-13  7:28         ` Dale
2007-01-13  5:03   ` Bo Ørsted Andresen
2007-01-13  4:22 ` Bo Ørsted Andresen
2007-01-13  4:57   ` [gentoo-user] " »Q«
2007-01-13  5:09   ` [gentoo-user] " Willie Wong
2007-01-13  6:04     ` Bo Ørsted Andresen
2007-01-13 12:31 ` Neil Bothwick
2007-01-13 17:30   ` Willie Wong
2007-01-13 20:48     ` Neil Bothwick

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=45A87BFE.5000300@exceedtech.net \
    --to=dalek@exceedtech.net \
    --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