[MacPorts] #29523: Strange definition of "future"

MacPorts noreply at macports.org
Sat May 21 05:13:31 PDT 2011


#29523: Strange definition of "future"
------------------------------------+---------------------------------------
 Reporter:  mattalbright@…          |       Owner:  macports-tickets@…                   
     Type:  defect                  |      Status:  new                                  
 Priority:  Normal                  |   Milestone:                                       
Component:  base                    |     Version:  1.9.2                                
 Keywords:                          |        Port:                                       
------------------------------------+---------------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@…, raimue@… (added)
  * component:  ports => base


Old description:

> Future: "You keep using that word. I do not think it means what you think
> it means."
>
> From
> http://svn.macports.org/repository/macports/trunk/base/src/port1.0/portutil.tcl
> :
>
> if {[file mtime ${portpath}/Portfile] >= [clock seconds]} {
>     return -code error "Portfile is from the future - check date and time
> of your system"
> }
>
> I'm pretty sure "future" means mtime > now, not >=.  I'm syncing a
> Portfile from an RCS and building it in a script, and apparently my
> computer is too fast, cause it's getting this error about the future.
>
> Yes, a `sleep 1` works, but c'mon!  :-)

New description:

 Future: "You keep using that word. I do not think it means what you think
 it means."

 From
 http://svn.macports.org/repository/macports/trunk/base/src/port1.0/portutil.tcl
 :

 {{{
 if {[file mtime ${portpath}/Portfile] >= [clock seconds]} {
     return -code error "Portfile is from the future - check date and time
 of your system"
 }
 }}}

 I'm pretty sure "future" means mtime > now, not >=.  I'm syncing a
 Portfile from an RCS and building it in a script, and apparently my
 computer is too fast, cause it's getting this error about the future.

 Yes, a `sleep 1` works, but c'mon!  :-)

--

Comment:

 This seems like a valid complaint, and I have encountered this problem
 myself when I am especially quick about pressing Command-S in the editor,
 Command-Tab to return to the Terminal, Up Arrow to repeat the last "sudo
 port install" command, and Return to execute it, all in less than one
 second. Rainer, you added this check in r65246. Any reason not to change
 it as the reporter indicates?

-- 
Ticket URL: <https://trac.macports.org/ticket/29523#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list