public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to degrade Gentoo system with webrsync method?
Date: Sun, 9 Jan 2022 14:46:17 +0000	[thread overview]
Message-ID: <b14babdb-db1a-0cc8-87ab-273f450bd8d2@youngman.org.uk> (raw)
In-Reply-To: <0520fc39-506a-340e-092c-05e671366862@gmail.com>



On 09/01/2022 13:39, Dale wrote:
> As a starting point, check the ebuild and see what all packages are
> listed there that it depends on.  Put the needed entries in package.mask
> and then use your world upgrade command plus -p to see what emerge wants
> to upgrade.  Keep adding until it is reporting nothing to upgrade.  The
> packages in the ebuild should help save some time.  I can't think of a
> easier way to do it.  Someone else may have ideas tho.  Oh, don't forget
> the ">=" signs and to specify versions.  Can't recall if it matters
> which symbol comes first.

Or do you want to use package.accept_keywords

I had a package that was in testing, so I've ended up creating a file in 
there called - I think the package was avidemux so that's what it's 
called ...

But in there it has the line(s)

=package.version ~amd64

I've deliberately used the "=" so for it, and every package it depends 
on, that version will be accepted. Aiui, if the stable version goes 
above that it will then upgrade to the stable version, so that my system 
will be pretty much just stable packages.

I also made the mistake of doing

ACCEPT_KEYWORDS="~amd64" emerge blah blah ...

which upgraded glibc! So now I need to configure this to keep the 
current version of glibc and wait till the stable version goes past.

Cheers,
Wol


  parent reply	other threads:[~2022-01-09 14:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 11:47 [gentoo-user] How to degrade Gentoo system with webrsync method? gevisz
2022-01-09 12:07 ` Arve Barsnes
2022-01-09 12:16   ` gevisz
2022-01-09 12:42     ` Dale
2022-01-09 13:13       ` gevisz
2022-01-09 13:39         ` Dale
2022-01-09 14:15           ` gevisz
2022-01-09 14:46           ` Wol [this message]
2022-01-09 17:08             ` Neil Bothwick
2022-01-11  1:48         ` Daniel Frey
2022-01-19 12:51 ` Robert David

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=b14babdb-db1a-0cc8-87ab-273f450bd8d2@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --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