unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Romain Francoise <romain@orebokech.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: [PATCH] POSIX ACL support
Date: Mon, 19 Nov 2012 22:33:16 +0100	[thread overview]
Message-ID: <87ehjpp9b7.fsf@silenus.orebokech.com> (raw)
In-Reply-To: <jwvtxsl1n47.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 19 Nov 2012 13:11:55 -0500")

Hi everyone,

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> This is really a general comment, not an issue with your patch in
>> particular, so don't let it distract. I just wonder if it is possible to
>> find a different way to pass this information around, so that we don't
>> need to have an ever increasing list of function arguments and return
>> values (preserve-this, preserve-that, preserve-the-other, etc...).
>> I don't have a good suggestion for how to do that.
>> (I have a vague memory this was mentioned when SELinux was added.)

> Yes, that's a problem.  We should consolidate `modes', `context', and
> `acl' into a `metadata' argument.

Ok, in files.el I can refactor the code to pass all the metadata in one go
and avoid the extra ACL argument here and there, no problem.

However, I think Glenn was also referring to the additional argument to
`copy-file', which doesn't preserve the modes. But maybe we can change the
existing `preserve-selinux-context' argument into a more general
`preserve-platform-attributes' argument and do both ACL and SELinux? Any
caller that wants to preserve the SELinux context probably wants to
preserve the ACL entries as well, anyway.

Ideally we'd get rid of `file-modes', `file-selinux-context' and
`file-posix-acl' and just add the info to `file-attributes', which already
returns a list of 12 different attributes. Then `set-file-attributes'
would be created to set all those different attributes in one go. But that
would be a lot of work...

Thanks!



  reply	other threads:[~2012-11-19 21:33 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18 22:27 [PATCH] POSIX ACL support Romain Francoise
2012-11-19  3:44 ` Eli Zaretskii
2012-11-19 21:41   ` Romain Francoise
2012-11-20  3:44     ` Eli Zaretskii
2012-11-19 17:11 ` Glenn Morris
2012-11-19 17:47   ` Eli Zaretskii
2012-11-19 18:11   ` Stefan Monnier
2012-11-19 21:33     ` Romain Francoise [this message]
2012-11-20 18:15       ` Stefan Monnier
2012-11-21 12:51         ` Romain Francoise
2012-11-21 14:25           ` Stefan Monnier
2012-11-21 15:36             ` Paul Eggert
2012-11-21 16:01               ` Romain Francoise
2012-11-21 18:17               ` Eli Zaretskii
2012-11-21 18:25                 ` Paul Eggert
2012-11-21 19:09                   ` Achim Gratz
2012-11-21 19:40                     ` Eli Zaretskii
2012-11-21 19:52                       ` Achim Gratz
2012-11-19 21:55     ` Paul Eggert
2012-11-20 18:16       ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ehjpp9b7.fsf@silenus.orebokech.com \
    --to=romain@orebokech.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).