From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LpRVM-0001fA-Au for garchives@archives.gentoo.org; Thu, 02 Apr 2009 18:19:08 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 1FABEE011F; Thu, 2 Apr 2009 18:19:07 +0000 (UTC) Received: from lbg2.evolone.org (evolone.org [198.145.28.177]) by pigeon.gentoo.org (Postfix) with ESMTP id E8E4CE011F for ; Thu, 2 Apr 2009 18:19:06 +0000 (UTC) Received: from lappy.evolone.org (unknown [192.168.1.100]) (Authenticated sender: col) by lbg2.evolone.org (Postfix) with ESMTPA id 594961BE0B for ; Thu, 2 Apr 2009 11:19:06 -0700 (PDT) Date: Thu, 2 Apr 2009 11:19:30 -0700 From: Michael Higgins To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] How to "freeze" my Gentoo system Message-ID: <20090402111930.30fce156@lappy.evolone.org> In-Reply-To: <200903120956.47288.alan.mckinnon@gmail.com> References: <20090311134054.4a4de361@lappy.evolone.org> <200903120956.47288.alan.mckinnon@gmail.com> Organization: Evolone X-Mailer: Claws Mail 3.7.1 (GTK+ 2.14.7; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: d7494c04-df5d-4c07-8374-bf26ada2f594 X-Archives-Hash: 1a9ca32160a49262613edbede7224336 On Thu, 12 Mar 2009 09:56:47 +0200 Alan McKinnon wrote: > On Wednesday 11 March 2009 22:40:54 Michael Higgins wrote: > > Don't know the proper term, but I want to stop version updates for > > a while, yet allow package-rN updates... > > This doesn't seem to be a built-in feature of portage after a quick > scan of the man pages. But I can think of a method to do it the long > way round: > > The atom syntax you want is Well, I finally got a tuit, the round type, and applied to this question. I don't know about >~ or ~> syntax. Not sure if ~ will work in package mask. Maybe in package.unmask, though... which makes sense, to my understanding. To unmask ~anyversionof-1.2.3. But to package.mask? I can't make '~' work. So... what I want, I think, is >= in package.mask for the *next* version update, so it doesn't get pulled in anywhere. Here's the command line I used: qatom $(qlist -ICv) | awk '{print ">="$1"/"$2"-"$3}' |\ sort -u | perl -pe 's/^(.+(?:\.|-))(\d+)(?>([-_.\da-z]*))$/$1.($2+1)/ge' | \ grep -Pv $( echo $( eix -inc -\* |cut -d " " -f 2 ) |tr " " "|" ) >> /etc/portage/package.mask Anyway, that is what I wound up with. Unless I'm totally off, it works by removing funky version strings (that hideous regex) and bumping up by a digit whatever is left, skipping anything that is slotted (eix -inc). (We can't mask in a slot, AFAIK, but maybe someone else does know.) I deeply, newly updated system and world, ran the script above and repeated the deep new update to system and world. The list passed, in that I didn't mask any currently installed packages. '-) And today I got no updates to install after syncing the tree. Good so far. Time will tell, of course, if this really works. If there are no ebuilds offered with revision numbers, or new -rc -pre -whatever, I won't be bothered by them, is the plan. That is, if portage doesn't see 1.2.-rc_9999 as >=1.3 -- which is shouldn't, right? ;-) Then one day I'll remove my additions to package.mask and spend a day pulling out my hair (or watching the new, magic portage do it's beautiful thing...) but that's better than possibly doing that several times a month. And this without ignoring any revisions, bug fixes, and the like. Cheers, -- |\ /| | | ~ ~ | \/ | |---| `|` ? | |ichael | |iggins \^ / michael.higgins[at]evolone[dot]org