Re: [91865] trunk/dports/science/netcdf-cxx/Portfile

2012-04-12 Thread Jeremy Lavergne
Modified: trunk/dports/science/netcdf-cxx/Portfile === --- trunk/dports/science/netcdf-cxx/Portfile 2012-04-12 03:38:31 UTC (rev 91864) +++ trunk/dports/science/netcdf-cxx/Portfile 2012-04-12 03:44:42 UTC (rev 91865) @@ -5,7

Re: [91865] trunk/dports/science/netcdf-cxx/Portfile

2012-04-12 Thread Joshua Root
On 2012-4-13 00:20 , Jeremy Lavergne wrote: When the epoch gets put back in, you'll also need to update the revision. epoch: 1 version: 4.2 revision: 2 The bug in the registry API that necessitates that is gone in 2.1 BTW. - Josh ___ macports-dev

Re: [91865] trunk/dports/science/netcdf-cxx/Portfile

2012-04-12 Thread Eric Cronin
On 12.04.2012 10:34, Joshua Root wrote: On 2012-4-13 00:20 , Jeremy Lavergne wrote: When the epoch gets put back in, you'll also need to update the revision. epoch: 1 version: 4.2 revision: 2 The bug in the registry API that necessitates that is gone in 2.1 BTW. Wasn't there a second

Re: [91865] trunk/dports/science/netcdf-cxx/Portfile

2012-04-12 Thread Joshua Root
On 2012-4-13 04:47 , Eric Cronin wrote: On 12.04.2012 10:34, Joshua Root wrote: On 2012-4-13 00:20 , Jeremy Lavergne wrote: When the epoch gets put back in, you'll also need to update the revision. epoch: 1 version: 4.2 revision: 2 The bug in the registry API that necessitates that is

Re: [91865] trunk/dports/science/netcdf-cxx/Portfile

2012-04-12 Thread Eric Cronin
On Apr 12, 2012, at 11:19 PM, Joshua Root wrote: On 2012-4-13 04:47 , Eric Cronin wrote: On 12.04.2012 10:34, Joshua Root wrote: On 2012-4-13 00:20 , Jeremy Lavergne wrote: When the epoch gets put back in, you'll also need to update the revision. epoch: 1 version: 4.2 revision: 2 The

Re: [91865] trunk/dports/science/netcdf-cxx/Portfile

2012-04-12 Thread Joshua Root
On 2012-4-13 13:40 , Eric Cronin wrote: On Apr 12, 2012, at 11:19 PM, Joshua Root wrote: On 2012-4-13 04:47 , Eric Cronin wrote: Wasn't there a second issue that the filenames for packages don't include epoch, so there is a risk of grabbing/reusing the package from a different epoch if the