On Sun, 22 Feb 2015 18:17:00 +1300
Kent Fredric kentfred...@gmail.com wrote:
For instance, perhaps a sysadmin simply wants to lock up GCC and make,
having a straight forward way do to that in bashrc would help them
achieve that, without them having to dish out a full ACL/LDAP setup,
and
On Sat, 21 Feb 2015, Ulrich Mueller wrote:
Personally, I think that controlling who is allowed to run certain
types of applications via group membership is a great idea. We should
introduce that approach for other applications too. How about an
editors group? Text editors are potentially
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/21/2015 01:35 AM, Ulrich Mueller wrote:
On Fri, 20 Feb 2015, Daniel Campbell wrote:
When this becomes more widespread, what action are users urged
to take in order to migrate to the new system? Should our
everyday user account be removed
On 22 February 2015 at 15:35, Daniel Campbell cont...@sporkbox.us wrote:
Personally, I think that controlling who is allowed to run certain
types of applications via group membership is a great idea. We
should introduce that approach for other applications too. How
about an editors
On 22 February 2015 at 18:06, Gordon Pettey petteyg...@gmail.com wrote:
Protect the permissions on the files, not the editors - there's always
another way to get content into a file if you have write permission to it.
If you try to do that with a g+xo-x, then you're going to have to do the
On 02/21/2015 01:35 AM, Ulrich Mueller wrote:
Personally, I think that controlling who is allowed to run certain
types of applications via group membership is a great idea. We
should introduce that approach for other applications too. How
about an editors group? Text editors are
On Fri, 20 Feb 2015, Daniel Campbell wrote:
When this becomes more widespread, what action are users urged to
take in order to migrate to the new system? Should our everyday
user account be removed from the `games` group, and the group should
be removed altogether?
Currently, users need not
Hi all,
As decided by the Council in its 20140812 meeting [1], every developer
is allowed to commit and maintain games ebuilds. Furthermore:
| There is consensus amongst council members that specific policies
| (e.g., games group, /usr/games hierarchy, and games.eclass) should
| be settled by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 02/19/2015 06:19 AM, Ulrich Mueller wrote:
Hi all, As decided by the Council in its 20140812 meeting [1],
every developer is allowed to commit and maintain games ebuilds.
Furthermore:
| There is consensus amongst council members that
