Best way to update packages from live ebuilds?

[sotn3m]

[Moderator note: Since this thread was raised from its ten year sleep, changed title from 9999 to be a bit more descriptive. -Hu]

As far as I read, all ebuild marked -9999 are not updated in any way during standard emerge update.

Question: Is there a nice way to (occasionally) re-emerge ALL -9999 packages in the system?

[PaulBredbury]

Yeah, write a script

~/bin/emergecvs

Code: Select all

#!/bin/sh
# Emerges my cvs ebuilds

emerge geany
emerge darkplaces
emerge wine
emerge nvclock

[sotn3m]

That is my idea also, but:

Is there a tool or sth, that can be used to find packages with version 9999? It would be more simple and more elegant. And there won't be a necessity to update the script too..

[PaulBredbury]

To find them:

Code: Select all

find /var/db/pkg/ -mindepth 2 -maxdepth 2 -name \*-9999

[sotn3m]

Base on that, command that re-emerges all "-9999" packages;)

Code: Select all

emerge -av `find /var/db/pkg/ -mindepth 2 -maxdepth 2 -name \*-9999|awk -F \/ '{printf "=%s/%s ", $5, $6}'`

Thx;)

[ashtophet]

The problem with this solution is that packages are not build in the appropiate order (necessary i.e. when you want to update e17) and not all CVS/SVN/git packages follow the -9999.

I'm using paludis, so --dl-reinstall-scm weekly works sweetly (not only with packages marked as *-9999, but also cvs, svn, live...).

[sotn3m]

I understand that migration from portage to paludis is a one-way trip?

Do you consider paludis to be stable and functional complete to move to it from portage? Are there many problems with ebuild compatibility?

I seems to be a really nice alternative, but I am worried not to destroy my system...

Nevertheless, it's great to see that such a tool is being developed.

[ashtophet]

Migration is not a one-way trip, you can revert to portage when you want to.

Maybe you'll find some ebuilds which don't play well with paludis strictness (I've only found them related to overlays, with plain easy fixing). Apart from that, I've been using paludis exclussively since a couple of months (exactly since Dec '06) and none of my kittens have been killed

If you want to try it out, just read the documentation on http://www.paludis.org (FAQ, Portage differences and Migration Guide are a must-read). If you find any trouble don't covered there I'm sure you'll find help at paludis thread: https://forums.gentoo.org/viewtopic-t-5 ... ight-.html [1]

If you switch you'll find:

- Increased speed.
- Better 3rd party overlays support (you won't need layman anymore, a paludis --sync will sync all your repositories, or any of them, at your request).
- scm (live, 999...) ebuild updating support.
- And much more (of course, you'll probably find 'features' you won't like )

----------------------------------------------------------
[1] If you have more questions about paludis features and migration please post them (after RTFM ) there as I didn't mean to hijack this thread.

[lyallp]

use app-portage/smart-live-rebuild

Code: Select all

	    # app-portage/smart-live-rebuild for rebuilding 9999 packages
	    # Could use simply "emerge @live-rebuild" but...
	    #  A smart replacement for various live package rebuilding
	    #  solutions. smart-live-rebuild tries to update the source checkouts of live
	    #  packages and calls emerge to rebuild those which are out-of-date.
	    #
	    if [ -x /usr/bin/smart-live-rebuild ]
	    then
		    echo "smart-live-rebuild..."
		    smart-live-rebuild
	    fi

[Zucca]

Holy-gravedigger, Batman!

[lyallp]

I have a couple of 9999 builds installed and found this thread when checking how to update.
Since it came top of lists, I thought I might as well provide the answer

[Zucca]

I thought I might as well provide the answer :)

Yeah. I'm actually with you in this. It's usually a good practice to provide the solution in case some one else stumble upon the topic. Especially in this case where the topic is still relevant on this day.

[khayyam]

et al ... not sure what app-portage/smart-live-rebuild does (is it in fact checking that such packages are "out-of-date" and so skip those that are not?) ... but the following is what I generally use.

Code: Select all

# emerge -a $(awk '{print "="$1}' <(qlist -ICv 9999))

best ... khay

[asturm]

(is it in fact checking that such packages are "out-of-date" and so skip those that are not?)

That is exactly what it does.

[Zucca]

the following is what I generally use.

Code: Select all

# emerge -a $(awk '{print "="$1}' <(qlist -ICv 9999))

This is why I use *nix systems.
And I get comments like "Why do you have to go the hard route and type everything, when you can just use some GUI application designed to it?" from windows users whenever I try to explain why command line is as good as it is.

[Ant P.]

et al ... not sure what app-portage/smart-live-rebuild does (is it in fact checking that such packages are "out-of-date" and so skip those that are not?)

It's a bit smarter than that: it detects live ebuilds via the presence of a VCS eclass in the metadata, rather than guessing version numbers (your example would work for 99.9% of cases I know about, but the "9999" is still just an informal convention), and then pings the remote server using `git ls-remote` or equivalent to see if there's any reason to update.

[xaviermiller]

and

Code: Select all

emerge @live-rebuild

?

[asturm]

It rebuilds all live packages regardless of git commits since last merge.