Ditto Ryan's reply. That said, I think SVN is actually OK for what
MacPorts needs. I greatly prefer GIT for actual software development,
because of the cloning, committing, branching, splitting, merging it
provides (offline or online, parts or whole, lots of usable options). I
use SVN for the MP tr
On Jan 4, 2016, at 5:13 PM, René J.V. Bertin wrote:
> You're aware that the full path to the lockfile is already printed, almost as
> if to allow people who know what they're doing to copy/paste it into a
> different terminal window and remove it.
you're assuming a lot there.
> An option to ig
+1 to making the locking work better
-1 to René's idea of adding a 'maybe destroy your macports install' option.
> On Jan 4, 2016, at 5:01 PM, Jeremy Lavergne
> wrote:
> When using trace mode and armed with the dependency tree, I know that my
> concurrent installs will not be impacting each oth
On Monday January 04 2016 16:18:54 Daniel J. Luke wrote:
> The consequences of ignoring the lock (in the worst case) are worse than -n
> -p or -o
You're aware that the full path to the lockfile is already printed, almost as
if to allow people who know what they're doing to copy/paste it into a
When using trace mode and armed with the dependency tree, I know that my
concurrent installs will not be impacting each other. The lock should be
intelligent enough to use the dependency tree�after all, MacPorts is the
one computing it.
I agree with Rene here: the lock should be smart enough to
On Jan 4, 2016, at 4:13 PM, René J.V. Bertin wrote:
> Maybe the "simplest" solution would be to provide an option to ignore the
> lock if it's present, and leave it to the user to know what s/he is doing
> (and assume the consequences, like with -n, -p or -o)?
that's a pretty horrible idea.
Th
On Wednesday November 18 2015 13:01:22 Rainer Müller wrote:
>As I said, there is potential to allow certain operations with
>fine-grained locking, but it requires more planning to get this right.
>Just enforcing serialization of all actions that modify the registry is
>the easy solution that works
Hi Ryan,
On Fri, Jan 01, 2016 at 11:43:17PM -0600, Ryan Schmidt wrote:
> How do you commit to the MacPorts Subversion repository?
>
> Using a Subversion working copy and "svn commit"?
This.
> Using a Git clone and git-svn?
> Some other method?
>
> Do you have any complaints about that method o
This is just to let you know that we now have Perl 6 in MacPorts.
We don't ship any modules (modules are installed to ~/.perl6 with
'panda' – the equivalent of cpan).
You can install it with
sudo port install rakudo panda
and install modules with
panda install Task::Star
Feedback and (u
I would be more likely to request commit privileges if there were a git option.
Maybe I need to look into the git clone with git-svn method.
-Sterling
On Jan 1, 2016, at 9:43PM, Ryan Schmidt wrote:
> Quick survey for committers:
>
> How do you commit to the MacPorts Subversion repository?
>
> On Jan 4, 2016, at 12:56 AM, dev...@macports.org wrote:
>
> Revision
> 144186
> Author
> dev...@macports.org
> Date
> 2016-01-03 22:56:45 -0800 (Sun, 03 Jan 2016)
> Log Message
>
> misc ports: increment revision to remove references to libncurses.5.
> Modified Paths
>
> • trunk/dports/
On Jan 3, 2016, at 8:22 PM, khindenb...@macports.org wrote:
>
> Revision
> 144182
> Author
> khindenb...@macports.org
> Date
> 2016-01-03 18:22:43 -0800 (Sun, 03 Jan 2016)
> Log Message
>
> gant: port fixes from #29303; change to github
> Modified Paths
>
> • trunk/dports/java/gant/Portfil
12 matches
Mail list logo