Skip to content

Open to pull requests for quick note/hint that this library is different from setfacl? #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
salk31 opened this issue Mar 15, 2025 · 1 comment

Comments

@salk31
Copy link

salk31 commented Mar 15, 2025

Hi,

As a random python developer migrating some code from using setfacl command and being new to ACLs, never mind libacl, I foolishly dived in feeding pylibacl strings similar to setfacl. Looking at some of the older issues it looks like I'm not the first.

Would you be up for pull requests to try and add a note to README warning people of this?

Also possibly tempt you to a tiny code example (further down the README maybe) making it clear about providing u::rwx,g:rwx,o:rwx, must provide a mask or call calc_mask... , d:u:1:rw not being a thing etc for fellow geeks in a rush?

Many thanks for this code. I'm writing code to manage millions of files being recalled from billions and this code is a life saver.

Cheers

Sam

@iustin
Copy link
Owner

iustin commented Mar 15, 2025

Hi there,

I'm happy for any and all pull requests, of course! I don't have much free time, so any contributions are welcome, even if only documentation.

Now, whether they will be accepted, that depends of course, and we'll see in specific cases. But please do send pull requests, I appreciate it.

And thanks for the kind words on the usefulness of this - I started writing it way way back, but I have no idea how useful it is, or if at all. Much appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants