public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org, rajiv@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-power/nut: ChangeLog nut-2.2.1.ebuild
Date: Sat, 15 Mar 2008 00:20:31 -0700	[thread overview]
Message-ID: <20080315072031.GA6852@comet> (raw)
In-Reply-To: <E1JYEd5-0003cP-9K@stork.gentoo.org>

On 06:03 Sun 09 Mar     , Rajiv Aaron Manglani (rajiv) wrote:
> 1.1                  sys-power/nut/nut-2.2.1.ebuild
> 
> file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-power/nut/nut-2.2.1.ebuild?rev=1.1&view=markup
> plain: http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-power/nut/nut-2.2.1.ebuild?rev=1.1&content-type=text/plain

> src_install() {

...

> 	eval fperms 0640 ${NUT_PRIVATE_FILES}
> 	eval fowners root:nut ${NUT_PRIVATE_FILES}
> 
> 	eval fperms 0644 ${NUT_PUBLIC_FILES}
> 	eval fowners root:root ${NUT_PUBLIC_FILES}

...

> pkg_postinst() {
> 	# this is to ensure that everybody that installed old versions still has
> 	# correct permissions
> 
> 	chown nut:nut "${ROOT}"/var/lib/nut 2>/dev/null
> 	chmod 0700 "${ROOT}"/var/lib/nut 2>/dev/null
> 
> 	eval chown root:nut "${ROOT}"${NUT_PRIVATE_FILES} 2>/dev/null
> 	eval chmod 0640 "${ROOT}"${NUT_PRIVATE_FILES} 2>/dev/null
> 
> 	eval chown root:root "${ROOT}"${NUT_PUBLIC_FILES} 2>/dev/null
> 	eval chmod 0644 "${ROOT}"${NUT_PUBLIC_FILES} 2>/dev/null

Is there any reason why eval is used in either of these places?

Thanks,
Donnie
-- 
gentoo-dev@lists.gentoo.org mailing list



       reply	other threads:[~2008-03-15  7:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1JYEd5-0003cP-9K@stork.gentoo.org>
2008-03-15  7:20 ` Donnie Berkholz [this message]
2008-03-15 18:26   ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in sys-power/nut: ChangeLog nut-2.2.1.ebuild Jeroen Roovers
2008-03-24 11:52   ` Mike Frysinger

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=20080315072031.GA6852@comet \
    --to=dberkholz@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=rajiv@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