Re: Moving to GitHub: Status Update, Action Required

2016-10-21 Thread Michael 

On 2016-10-21, at 8:03 PM, Lawrence Velázquez  wrote:

>> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt  wrote:
>> 
>>> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez  wrote:
>>> 
 On Oct 21, 2016, at 10:20 PM, Craig Treleaven  
 wrote:
 
 Also, is the consensus that a graphical user interface over git
 more likely to be harmful than helpful?  The Tools section at the
 bottom of the page doesn’t give any kind of recommendation.
>>> 
>>> I don't know that there is any sort of consensus on that. Everyone
>>> has their own preferences, and Git is almost absurdly flexible about
>>> workflows. I don't think our documentation should recommend any
>>> particular tools.
>> 
>> I think it would be reasonable for us to mention that GitHub Desktop
>> is a GUI client that exists and works for basic operations like
>> creating or switching between branches and committing changes and has
>> a handy diff viewer to see your changes before committing and even
>> lets you select which portions of your diff you want to commit. But it
>> is of no help with even slightly more advanced git commands.
> 
> Sure, we should certainly list more tools; that section is a bit sparse.
> I just meant that we shouldn't recommend any one tool over the others
> (e.g., "if you like GUI tools, you should use X").

The first thing I noticed not mentioned in that doc was "git gui". While you do 
mention that you can commit multiple changes, separately, before pushing it all 
out, the question is, how do you separate a bunch of edits into several 
separate commits.

"git gui", for me, is an invaluable tool for reviewing changes before 
committing them, and for breaking changes into several commits. This looks like 
something that deserves to be mentioned as a "start here" tool.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [154110] trunk/base/portmgr/dmg/postflight.in

2016-10-21 Thread Ryan Schmidt 

> On Oct 21, 2016, at 8:01 PM, c...@macports.org wrote:
> 
> Revision
> 154110
> Author
> c...@macports.org
> Date
> 2016-10-22 03:01:24 +0200 (Sat, 22 Oct 2016)
> Log Message
> 
> Installer postflight: Fix useless test $OUR_STRING used to contain a 
> timestamp down to second precision, which makes it very unlikely to hit a 
> match. grep for something more likely to match instead.

This resolves https://trac.macports.org/ticket/43749, right?

If so, we should merge this to the 2.3 branch.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Moving to GitHub: Status Update, Action Required

2016-10-21 Thread Lawrence Velázquez 
> On Oct 21, 2016, at 10:20 PM, Craig Treleaven  wrote:
> 
> However, would it be possible to add a tangible example of updating
> a port to that page?  
> 
> I know a little bit about Subversion and less about Git.  I would like
> to see a soup-to-nuts example of cloning the ports tree, updating
> a Portfile, maybe deleting an old patch and adding a new one, and
> getting the updated port into MacPorts (direct commit v. pull
> request).  It would be helpful if one-time requirements (setting name
> and email address) were clearly separated from repetitive steps
> (pulling changes from master?).  Otherwise, it is going to be a wee
> bit nerve-wracking the first few times...

This would be good.

> Also, is the consensus that a graphical user interface over git more
> likely to be harmful than helpful?  The Tools section at the bottom of
> the page doesn’t give any kind of recommendation.

I don't know that there is any sort of consensus on that. Everyone has
their own preferences, and Git is almost absurdly flexible about
workflows. I don't think our documentation should recommend any
particular tools. 

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Moving to GitHub: Status Update, Action Required

2016-10-21 Thread Craig Treleaven 
> On Oct 21, 2016, at 2:12 PM, Clemens Lang  wrote:
> 
> Hello MacPorts users and developers,
> 
> ... Please read through
> https://trac.macports.org/wiki/WorkingWithGit
> which contains a number of guidelines for working with the MacPorts Git
> repositories.
> 
The Working with Git page is pretty good.  There is a lot of good background 
and explanation of why and how Git is different from svn.

However, would it be possible to add a tangible example of updating a port to 
that page?  

I know a little bit about Subversion and less about Git.  I would like to see a 
soup-to-nuts example of cloning the ports tree, updating a Portfile, maybe 
deleting an old patch and adding a new one, and getting the updated port into 
MacPorts (direct commit v. pull request).  It would be helpful if one-time 
requirements (setting name and email address) were clearly separated from 
repetitive steps (pulling changes from master?).  Otherwise, it is going to be 
a wee bit nerve-wracking the first few times...

Also, is the consensus that a graphical user interface over git more likely to 
be harmful than helpful?  The Tools section at the bottom of the page doesn’t 
give any kind of recommendation.

Craig
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Trac & Subversion available again

2016-10-21 Thread Clemens Lang 
Hello MacPorts users and developers,

On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
> Due to the current SVN and Trac downtime, we are also discussing to
> make the move of Trac sooner if that helps us restore service earlier.
> We will keep you informed on this.

Due to the current unplanned downtime, we brought the migration of our
Trac installation forward and finished it today. Pending DNS
propagation, you should be able to reach Trac at trac.macports.org
again. Note that you will need a GitHub account to log into Trac now.

Please make sure that you have added the email address you used in Trac
to your GitHub account. A cronjob will automatically associate your
tickets and other contributions with the GitHub login a few minutes
after your login.


The Subversion server svn.macports.org has also been moved and
committing works again. Please commit your pending work before October
29th.

-- 
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Moving to GitHub: Status Update, Action Required

2016-10-21 Thread Clemens Lang 
Hello MacPorts users and developers,

MacPorts will be moving to GitHub soon. We're sending this email to
inform you about changes in how you access the MacPorts repositories and
bug tracker. Additionally, this email contains information on planned
downtimes. 

Action Required: GitHub Accounts

Our new Trac installation will use GitHub for login. If you do not have
a GitHub account yet, please create one now at
 https://github.com/join

To help us match your previous contributions and Trac tickets to your
GitHub account, please go to
 https://github.com/settings/emails
and ensure that you have added and verified all email addresses you have
used for MacPorts Trac. There is no need for any of these addresses to
be the primary one, or even public. They just need to be listed and
verified.

If you are a MacPorts committer, please make sure that you have added
your @macports.org address.

Action Required by MacPorts Developers: Joining the GitHub Organization
===
If you are a MacPorts developer and have commit access, please send the
following mail to macports-in...@lists.macports.org:
 Subject: Please invite me to MacPorts on GitHub
 Content:
  Handle: 
We will send an invite to join the MacPorts organization on GitHub to
your MacPorts email address. Follow the steps in this invitation email
to get commit access to the MacPorts Git repositories and privileges in
Trac.

Migration Timeline
==
The switch to Git will happen on the weekend of October 29th/30th. We
will disable committing to the Subversion repository, run a last
incremental export to Git and push the changes to GitHub. If you have
commit access, please do not commit to the repositories at GitHub until
a mail to the list indicates the conversion is done. Please read through
 https://trac.macports.org/wiki/WorkingWithGit
which contains a number of guidelines for working with the MacPorts Git
repositories.

We will also place our old Trac instance in read-only mode and move the
tickets to our new instance. Note that the new Trac instance uses GitHub
for login. We recommend that you have added and verified all email
addresses that you used for filing tickets in Trac to your GitHub
account before you log in to the new Trac. For MacPorts developers, this
includes your MacPorts email address. This will allow us to
automatically transfer your tickets to your new user account.

Due to the current SVN and Trac downtime, we are also discussing to make
the move of Trac sooner if that helps us restore service earlier. We
will keep you informed on this.


On behalf of the MacPorts migration team,
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev