On Oct 17, 2013, at 23:45, Lawrence Velázquez wrote:
> On Oct 17, 2013, at 9:53 PM, Ryan Schmidt wrote:
>
>> Surely the macports user needs write permission to change things when
>> running "sudo port sync"?
>
> Is there a particular reason you need to run "sudo port sync"? I just run
> "port
On 2013-10-18 12:53 , Ryan Schmidt wrote:
>
> This has become increasingly difficult ever since the gsoc08-privileges
> branch was merged in and basically made non-root MacPorts installations
> unusable.
What problem(s) are you seeing with non-root installations? Have you
filed tickets?
I don'
On 2013-10-18 03:53, Ryan Schmidt wrote:
>
> On Oct 17, 2013, at 07:34, Clemens Lang wrote:
>
>> On Wed, Oct 16, 2013 at 08:18:51PM -0500, Ryan Schmidt wrote:
>>> If my main dports tree is a Subversion working copy, what are
>>> the recommended permissions and user and group ownership so that
>>
I am aware (and so should you be), that these files are editable by my
user account and contain code that will be run with super user
privileges – so if you're concerned about possible privilege
escalations, you should create the checkout as root (which also implies
you need root privileges to e
On Oct 17, 2013, at 9:53 PM, Ryan Schmidt wrote:
> Surely the macports user needs write permission to change things when running
> "sudo port sync"?
Is there a particular reason you need to run "sudo port sync"? I just run "port
sync" on my system, and everything works fine. (I own my Subversi
On Oct 17, 2013, at 07:34, Clemens Lang wrote:
> On Wed, Oct 16, 2013 at 08:18:51PM -0500, Ryan Schmidt wrote:
>> If my main dports tree is a Subversion working copy, what are the
>> recommended permissions and user and group ownership so that "sudo
>> port sync" and "svn update" and "svn commit
On Wed, Oct 16, 2013 at 08:18:51PM -0500, Ryan Schmidt wrote:
> If my main dports tree is a Subversion working copy, what are the
> recommended permissions and user and group ownership so that "sudo
> port sync" and "svn update" and "svn commit" all work? It seems like I
> should understand this by
On 2013-10-17 03:18, Ryan Schmidt wrote:
> If my main dports tree is a Subversion working copy, what are the
> recommended permissions and user and group ownership so that "sudo
> port sync" and "svn update" and "svn commit" all work? It seems like
> I should understand this by now but I'm not gett
If my main dports tree is a Subversion working copy, what are the recommended
permissions and user and group ownership so that "sudo port sync" and "svn
update" and "svn commit" all work? It seems like I should understand this by
now but I'm not getting it; what I'm getting are permission errors