From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Update of live ebuilds
Date: Sun, 07 Aug 2011 14:53:21 +0200 [thread overview]
Message-ID: <14606252.Pre6GFVvoc@nazgul> (raw)
In-Reply-To: <4E3E8931.8000504@gmail.com>
On Sun 07 August 2011 14:46:41 Natanael Olaiz did opine thusly:
> 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?
There is no tool to do this that I know of.
Regular ebuilds ( not -9999 versions) use release versions that do not
change, so working out the deps and changes is easy.
Live ebuilds by definition do not have versions, they only have
"whatever is in the tree right now". Commit numbers do not really
qualify as version numbers.
If you were a developer working on those projects you are using live
ebuilds for, you would know what has been updated recently and use
your brain smarts to figure out what to rebuild. or (as most do) you
would just rebuild the whole lot almost every day anyway.
By using live ebuilds you implicitly have given up the ability to have
version number tracking and have agreed to do it all yourself. It's
something you are just going to have to deal with, or downgrade back
to released versions.
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-08-07 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 12:46 [gentoo-user] Update of live ebuilds Natanael Olaiz
2011-08-07 12:53 ` Alan McKinnon [this message]
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=14606252.Pre6GFVvoc@nazgul \
--to=alan.mckinnon@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