[gentoo-user] Re: How to know when a package is due to go stable?
Justin wrote: James Homuth schrieb: There are several packages that were thrown around on the list, or versions of packages, that I've come across that I figure I might want to take an active interest in. However, to avoid sending my boxes into a tailspin, I'm staying away from installing the still in development versions. What I'd like to know though is if there's some means of knowing if/when, as an example, a newer version of Portage is supposed to be considered stable. If not then I can always keep an eye on the relevant RSS feeds, but it was mostly just curiosity on my part. Thanks either way. James Quite easy, emerge --sync emerge -up world system, then you know whats gone stable with higher versions. Or, to also cover packages not in world/system, you can do: emerge -p1u `qlist -IC` (Don't omit the 1 from the options or you'll mess up your world file with packages that are purely dependencies.) I wonder why emerge doesn't do something like this by default, actually. Say a package has a serious exploit and an update was made. If the package isn't in world, emerge will never grab the update.
Re: [gentoo-user] Re: How to know when a package is due to go stable?
On Fri, 31 Oct 2008 16:37:58 +0200, Nikos Chantziaras wrote: I wonder why emerge doesn't do something like this by default, actually. Say a package has a serious exploit and an update was made. If the package isn't in world, emerge will never grab the update. If it's not is world, or a dependency of a world package, it's not needed and --depclean will catch it. -- Neil Bothwick IBM - I Blame Microsoft signature.asc Description: PGP signature
[gentoo-user] Re: How to know when a package is due to go stable?
Neil Bothwick wrote: On Fri, 31 Oct 2008 16:37:58 +0200, Nikos Chantziaras wrote: I wonder why emerge doesn't do something like this by default, actually. Say a package has a serious exploit and an update was made. If the package isn't in world, emerge will never grab the update. If it's not is world, or a dependency of a world package, it's not needed and --depclean will catch it. No, it will not :P Don't ask me why, because I don't know. I only know from experience that --depclean does not catch some packages that get updated with emerge -1u `qlist -IC` (and don't get updated with emerge -uD world system).
RE: [gentoo-user] Re: How to know when a package is due to go stable?
-Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Nikos Chantziaras Sent: October 31, 2008 10:38 AM To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: How to know when a package is due to go stable? Justin wrote: James Homuth schrieb: There are several packages that were thrown around on the list, or versions of packages, that I've come across that I figure I might want to take an active interest in. However, to avoid sending my boxes into a tailspin, I'm staying away from installing the still in development versions. What I'd like to know though is if there's some means of knowing if/when, as an example, a newer version of Portage is supposed to be considered stable. If not then I can always keep an eye on the relevant RSS feeds, but it was mostly just curiosity on my part. Thanks either way. James Quite easy, emerge --sync emerge -up world system, then you know whats gone stable with higher versions. Or, to also cover packages not in world/system, you can do: emerge -p1u `qlist -IC` (Don't omit the 1 from the options or you'll mess up your world file with packages that are purely dependencies.) I wonder why emerge doesn't do something like this by default, actually. Say a package has a serious exploit and an update was made. If the package isn't in world, emerge will never grab the update. That'll teach me to just read the Gentoo documentation. I figured emerge --update --deep world covered system, too.
Re: [gentoo-user] Re: How to know when a package is due to go stable?
James Homuth wrote: That'll teach me to just read the Gentoo documentation. I figured emerge --update --deep world covered system, too. As far as what I was told on -dev, it still does. If you use the @system or @world, then that is a different thing. I'm assuming what I was told still holds true. Dale :-) :-) P.S. Yea, I'm back. I had a reaction to some meds and they dang near killed me. Spent about a week in the hospital wondering what that light was. o_O
Re: [gentoo-user] Re: How to know when a package is due to go stable?
On Fri, 31 Oct 2008 18:11:20 +0200, Nikos Chantziaras wrote: If it's not is world, or a dependency of a world package, it's not needed and --depclean will catch it. No, it will not :P Don't ask me why, because I don't know. I only know from experience that --depclean does not catch some packages that get updated with emerge -1u `qlist -IC` (and don't get updated with emerge -uD world system). Possibly build time dependencies, which aren't updated unless you use --with-bdeps y. -- Neil Bothwick There's too much blood in my caffeine system. signature.asc Description: PGP signature
