public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)?
Date: Tue, 20 Nov 2012 21:56:46 +0200	[thread overview]
Message-ID: <20121120215646.36303711@khamul.example.com> (raw)
In-Reply-To: <50ABD73D.7040308@libertytrek.org>

On Tue, 20 Nov 2012 14:17:17 -0500
Tanstaafl <tanstaafl@libertytrek.org> wrote:

> On 2012-11-20 12:05 PM, Bruce Hill <daddy@happypenguincomputers.com>
> wrote:
> > On Tue, Nov 20, 2012 at 08:46:59AM -0500, Tanstaafl wrote:
> >> Anyone?
> >>
> >> I don't see any news blurbs warning about it, but with everything
> >> going on with udev, systemd, etc, I'm not risking updating
> >> unless/until I know it is safe.
> 
> > Have you read the requirements in
> > /usr/portage/sys-apps/openrc/openrc-0.11.5.ebuild ?
> 
> I don't see anything in there labeled 'requirements'...
> 
> All I found was:
> 
> RDEPEND="virtual/init
>          kernel_FreeBSD? ( || ( >=sys-freebsd/freebsd-ubin-9.0_rc 
> sys-process/fuser-bsd ) )
>          elibc_glibc? ( >=sys-libs/glibc-2.5 )
>          ncurses? ( sys-libs/ncurses )
>          pam? ( sys-auth/pambase )
>          >=sys-apps/baselayout-2.1-r1
>          kernel_linux? (
>                  sys-process/psmisc
>          )
>          !<sys-fs/udev-133"
> 
> So, *maybe* the last line means it needs a udev not less than 133 -
> but I don't know enough about how ebuilds to work to risk an
> unbootable system if it doesn't mean what I think it means.
> 
> Sorry, I'm not a programmer and don't know what to look for (or even 
> where to look until you pointed me to the file), so how about just a 
> simple answer?

He probably means all the elogs and ewarns in there - that ebuild is
littered with the things. View the ebuild in less and search on
"equire", you'll see what I mean.

"!<sys-fs/udev-133" does indeed mean the ebuild requires udev that is
not less than 133. or put another way, it wants udev version 133 or
higher.




-- 
Alan McKinnon
alan.mckinnon@gmail.com



  reply	other threads:[~2012-11-20 20:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 13:46 [gentoo-user] OpenRC update to 0.11.5 - safe if using older udev (pinned to udev-181)? Tanstaafl
2012-11-20 14:36 ` Markos Chandras
2012-11-20 15:25   ` Tanstaafl
2012-11-20 17:05 ` Bruce Hill
2012-11-20 19:17   ` Tanstaafl
2012-11-20 19:56     ` Alan McKinnon [this message]
2012-11-20 21:43     ` Bruce Hill
2012-11-20 21:47     ` Bruce Hill
2012-11-20 19:38 ` Mark Knecht
2012-11-20 21:24   ` Mick

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=20121120215646.36303711@khamul.example.com \
    --to=alan.mckinnon@gmail.com \
    --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