public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bruce Hill <daddy@happypenguincomputers.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 15:43:44 -0600	[thread overview]
Message-ID: <20121120214344.GB26635@server> (raw)
In-Reply-To: <50ABD73D.7040308@libertytrek.org>

On Tue, Nov 20, 2012 at 02:17:17PM -0500, Tanstaafl wrote:
> 
> 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?

You are correct in that it requires !<sys-fs/udev-133, where ! means "not" and
< means "less than", so "not less than sys-fs/udev-133". The lowest version in
portage atm is 141-r1, so unless you had an extremely old udev and masked it,
you won't have trouble there.

If you continue to read the ebuild, using less as someone suggested, use the
slash (/) which searches, such as /openrc and /udev to read what the ebuild
will do. That ebuild is an awk script which is going to execute the commands
as you see them. This section, for instance:

# >=OpenRC-0.11.3 requires udev-mount to be in the sysinit runlevel with udev.
migrate_udev_mount_script() {
        if [ -e "${EROOT}"etc/runlevels/sysinit/udev -a \
                ! -e "${EROOT}"etc/runlevels/sysinit/udev-mount ]; then
                add_boot_init udev-mount sysinit
        fi
        return 0
}

Since sys-apps/openrc-0.11.5 is still ~arch (where arch is architecture, such
as x86, amd64; and ~ means unstable), you might find bugs. It has been
submittied for stable request https://bugs.gentoo.org/show_bug.cgi?id=435756
but not yet approved as stable.

Do you mind asking why you want to use unstable openrc? Is there some feature
you need?
-- 
Happy Penguin Computers               >')
126 Fenco Drive                       ( \
Tupelo, MS 38801                       ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting


  parent reply	other threads:[~2012-11-20 21:45 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
2012-11-20 21:43     ` Bruce Hill [this message]
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=20121120214344.GB26635@server \
    --to=daddy@happypenguincomputers.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