public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] How to degrade Gentoo system with webrsync method?
Date: Sun, 9 Jan 2022 17:08:24 +0000	[thread overview]
Message-ID: <20220109170824.2d261b34@digimed.co.uk> (raw)
In-Reply-To: <b14babdb-db1a-0cc8-87ab-273f450bd8d2@youngman.org.uk>

[-- Attachment #1: Type: text/plain, Size: 825 bytes --]

On Sun, 9 Jan 2022 14:46:17 +0000, Wol wrote:

> 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'd use ~ instead of = so it will accept -r1, -r2, etc. variants of that
version, to pick up any bug fixes. Once one of those variants, or a
higher version, becomes stable you'll be back on stable and
eix-test-obsolete will let you know you can remove the entry.


-- 
Neil Bothwick

Quality control, n.:
  Assuring that the quality of a product does not get out of hand
   and add to the cost of its manufacture or design.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-01-09 17:08 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
2022-01-09 17:08             ` Neil Bothwick [this message]
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=20220109170824.2d261b34@digimed.co.uk \
    --to=neil@digimed.co.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