From: Roy Marples <uberlord@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-apps/baselayout: ChangeLog baselayout-2.0.0_rc5.ebuild
Date: Fri, 12 Oct 2007 07:51:00 +0100 [thread overview]
Message-ID: <1192171860.3238.5.camel@uberpc.marples.name> (raw)
In-Reply-To: <20071012052521.GF23990@supernova>
On Thu, 2007-10-11 at 22:25 -0700, Donnie Berkholz wrote:
> > cp -p "${ROOT}usr/share/baselayout/${x}" ${ROOT}etc
> Two ROOT's to quote here, not just one. =)
Fixed, thanks
>
> > # We need to copy svcdir if upgrading
> > if has_version "<sys-apps/${PN}-1.13.0_alpha" ; then
> > (
> > . "${ROOT}etc/conf.d/rc"
> > svcdir="${svcdir:-/var/lib/init.d}"
> > einfo "Moving state from ${ROOT}${svcdir} to ${ROOT}lib/rcscripts/init.d"
> > cp -RPp "${ROOT}${svcdir}"/* "${ROOT}"lib/rcscripts/init.d
> > rm -rf "${ROOT}"lib/rcscripts/init.d/daemons \
> > "${ROOT}"lib/rcscripts/init.d/console
> > umount "${ROOT}${svcdir}" 2>/dev/null
> > rm -rf "${ROOT}${svcdir}"
> > )
>
> Can this be done in a code block instead, or do svdir and /etc/conf.d/rc
> sourcing pollute things too badly?
Possibly. There should not be any collisions, but should also doesn't
mean won't in the future. I chose to take no chances.
>
> > if has_version "<sys-apps/${PN}-1.13.0_alpha" ; then
> > (
> > . "${ROOT}etc/conf.d/rc"
> > svcdir="${svcdir:-/var/lib/init.d}"
> > einfo "Moving state from ${ROOT}lib/rcscripts/init.d to ${ROOT}${svcdir}"
> > mkdir -p "${ROOT}${svcdir}"
> > cp -RPp "${ROOT}lib/rcscripts/init.d"/* "${ROOT}${svcdir}"
> > rm -rf "${ROOT}${svcdir}"/daemons
> > umount "${ROOT}lib/rcscripts/init.d" 2>/dev/null
> > rm -rf "${ROOT}lib/rcscripts/init.d"
> > )
>
> Same question. Also, could this code, as well as the other cases I
> cropped out, simply be abstracted into a function instead?
Not really, they are different and I don't think you'd gain that much.
And for any avid readers of this ebuild, the similar functions for
baselayout-2 versions will be punted once it goes ~ARCH.
Thanks
Roy
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2007-10-12 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Ig0Ov-0007Wd-EC@stork.gentoo.org>
2007-10-12 5:25 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-apps/baselayout: ChangeLog baselayout-2.0.0_rc5.ebuild Donnie Berkholz
2007-10-12 6:51 ` Roy Marples [this message]
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=1192171860.3238.5.camel@uberpc.marples.name \
--to=uberlord@gentoo.org \
--cc=gentoo-dev@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