Re: move port to new category

2012-11-01 Thread Blair Zajac
On 11/1/12 7:50 PM, Ryan Schmidt wrote: On Nov 1, 2012, at 21:41, Blair Zajac wrote: Yes, but we still like to do 'svn copy' to retain history. Sure, for files that have a history. But in the past, if I needed to, say, add a patch to both graphviz and graphviz-devel, I would have added it t

Re: move port to new category

2012-11-01 Thread Blair Zajac
On 11/1/12 8:06 PM, Jeremy Lavergne wrote: I was referring to move here, not rebase/merge (although git is good at following renames in merges also). Sorry, it was meant as a warning to those getting their feet wet coming from subversion. I should have prefixed it with "Beware: "! Yes, def

Re: move port to new category

2012-11-01 Thread Jeremy Lavergne
> I was referring to move here, not rebase/merge (although git is good at > following renames in merges also). Sorry, it was meant as a warning to those getting their feet wet coming from subversion. I should have prefixed it with "Beware: "! ___ mac

Re: move port to new category

2012-11-01 Thread Blair Zajac
Regards, Blair On Nov 1, 2012, at 7:58 PM, Jeremy Lavergne wrote: >> git does that? Neat. I really need to read more of the git manual. > > Subversion terminology is not git terminology. Leave your assumptions about > rebase/merge at the door. I was referring to move here, not rebase/merge

Re: move port to new category

2012-11-01 Thread Jeremy Lavergne
> git does that? Neat. I really need to read more of the git manual. Subversion terminology is not git terminology. Leave your assumptions about rebase/merge at the door. ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.maco

Re: move port to new category

2012-11-01 Thread Ryan Schmidt
On Nov 1, 2012, at 21:41, Blair Zajac wrote: > Yes, but we still like to do 'svn copy' to retain history. Sure, for files that have a history. But in the past, if I needed to, say, add a patch to both graphviz and graphviz-devel, I would have added it to one, committed it, updated, then copied

Re: move port to new category

2012-11-01 Thread Blair Zajac
On 11/01/2012 07:08 PM, Ryan Schmidt wrote: On Nov 1, 2012, at 15:23, Blair Zajac wrote: If I have no other work to commit in my tree, I'll just do 'svn commit' instead of listing the paths to commit. In general, listing individual paths isn't a great idea, since it's a practice that can me

Re: move port to new category

2012-11-01 Thread Ryan Schmidt
On Nov 1, 2012, at 15:23, Blair Zajac wrote: > If I have no other work to commit in my tree, I'll just do 'svn commit' > instead of listing the paths to commit. In general, listing individual paths > isn't a great idea, since it's a practice that can mess up merging, where the > svn:mergeinfo

Re: move port to new category

2012-11-01 Thread Bradley Giesbrecht
On Nov 1, 2012, at 1:23 PM, Blair Zajac wrote: > On 11/01/2012 12:50 PM, Bradley Giesbrecht wrote: >> Is it good enough to move a port like so, or is there more to it? >> >> svn mv devel/levmar math/levmar >> port ed math/levmar # change category and revbump >> svn ci devel/levmar math/levmar >

Re: move port to new category

2012-11-01 Thread Rainer Müller
On 2012-11-01 21:23, Blair Zajac wrote: > On 11/01/2012 12:50 PM, Bradley Giesbrecht wrote: >> Is it good enough to move a port like so, or is there more to it? >> >> svn mv devel/levmar math/levmar >> port ed math/levmar # change category and revbump >> svn ci devel/levmar math/levmar > > That'll

Re: move port to new category

2012-11-01 Thread Blair Zajac
On 11/01/2012 12:50 PM, Bradley Giesbrecht wrote: Is it good enough to move a port like so, or is there more to it? svn mv devel/levmar math/levmar port ed math/levmar # change category and revbump svn ci devel/levmar math/levmar That'll work. Do you need the revbump though? If I have no oth

move port to new category

2012-11-01 Thread Bradley Giesbrecht
Is it good enough to move a port like so, or is there more to it? svn mv devel/levmar math/levmar port ed math/levmar # change category and revbump svn ci devel/levmar math/levmar Regards, Bradley Giesbrecht (pixilla) smime.p7s Description: S/MIME cryptographic signature _

Re: New Port to Tree Timeline

2012-11-01 Thread Ben Smith
I've already filed a ticket for each of the ports; I'm not sure filing another would be helpful. I know I get annoyed when I see duplicate tickets. However, if someone is interested these are the tickets for each of the ports: https://trac.macports.org/ticket/36690 (EGSimulation) http://trac.mac

Re: New Port to Tree Timeline

2012-11-01 Thread MK-MacPorts
It all depends if one of the main devs has time to look at it. File a ticket and attach your new portfile and you'll see whether someone is interested. Usually one of the most active guys picks it up within a few DAYS! :-) ___ macports-dev mailing list

New Port to Tree Timeline

2012-11-01 Thread Ben Smith
I went on portfile creating spree starting about a week ago; which was instigated by a script that I really would like available to others in concert with a paper I've submitted to an academic journal. So, here is my question, and I want to be clear this is just a question as I realize you are all