From: Natanael Olaiz <nolaiz@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Update of live ebuilds
Date: Sun, 07 Aug 2011 14:46:41 +0200 [thread overview]
Message-ID: <4E3E8931.8000504@gmail.com> (raw)
Hi all,
Someone knows a way to check for live ebuilds updates availability?
When upgrading my system, if I just do an 'emerge -u' that doesn't
include possible updates in live ebuilds. Then I need to force a
reinstallation of live ebuilds, that probably have no updates, resulting
a waste of time, or either do the repositories updates by hand (for
instance 'svn up') in the src dir, to decide if I need to reinstall the
ebuild..
I'd just found this thread about it:
http://forums.gentoo.org/viewtopic-t-518701-postdays-0-postorder-asc-start-0.html
But I was wondering: there is no other way/tool included in gentoo to do
this?
Thanks in advance.
Best regards,
Natanael.
next reply other threads:[~2011-08-07 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 12:46 Natanael Olaiz [this message]
2011-08-07 12:53 ` [gentoo-user] Update of live ebuilds Alan McKinnon
2011-08-07 13:04 ` Daniel Pielmeier
2011-08-08 14:35 ` [gentoo-user] " James
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=4E3E8931.8000504@gmail.com \
--to=nolaiz@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