From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] PATCH: Use lchown and lchgrp no-op functions when operating on symlinks (#99616)
Date: Fri, 22 Jul 2005 08:49:41 +0900 [thread overview]
Message-ID: <200507220849.43700.jstubbs@gentoo.org> (raw)
In-Reply-To: <20050721171701.GA27660@exodus>
[-- Attachment #1: Type: text/plain, Size: 1136 bytes --]
On Friday 22 July 2005 02:17, Brian D. Harring wrote:
> On Thu, Jul 21, 2005 at 11:13:34PM +0900, Jason Stubbs wrote:
> > diff -uNr portage-2.0.51.22-r2/bin/ebuild.sh portage-patched/bin/ebuild.sh
> > --- portage-2.0.51.22-r2/bin/ebuild.sh 2005-07-19 19:38:32.949904000 +0900
> > +++ portage-patched/bin/ebuild.sh 2005-07-21 23:03:58.429898000 +0900
> > @@ -85,6 +85,11 @@
> > export SANDBOX_PREDICT="$SANDBOX_PREDICT:$1"
> > }
> >
> > +lchown()
> > +{ 0; }
> > +
> > +lchgrp()
> > +{ 0; }
>
> Default being negation of funcs, and forcing profiles to override it?
> Why not reverse it, a default func that works, with profiles
> overriding if/when it doesn't work?
I don't really like the idea of adding yet another >& /dev/null. With a GNU
userland, it would be something like:
lchown()
{ chown -h $* }
If the many errors that will occur when the userland's chown doesn't support
this flag are okay, putting in working defaults are fine. The main reasons I
went with no-ops are that symlink ownership is purely cosmetic (afaik) and
to try to keep userland specific stuff out.
--
Jason Stubbs
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-07-21 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-21 14:13 [gentoo-portage-dev] PATCH: Use lchown and lchgrp no-op functions when operating on symlinks (#99616) Jason Stubbs
2005-07-21 17:17 ` Brian D. Harring
2005-07-21 23:49 ` Jason Stubbs [this message]
2005-08-05 3:31 ` [gentoo-portage-dev] PATCH: properly handle metadata transfer on first sync of an empty tree (#96410) Brian D. Harring
2005-08-05 11:20 ` Jason Stubbs
2005-08-09 7:19 ` Brian Harring
2005-08-06 23:30 ` Zac Medico
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=200507220849.43700.jstubbs@gentoo.org \
--to=jstubbs@gentoo.org \
--cc=gentoo-portage-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