Hi I am working on e17 stuff and here is what happened after installing evas 0.9.9.037 while the Portindex refenrence is still at 0.9.9.010 : Bilbo:~/macports/dports yves$ port outdated The following installed ports are outdated: evas 0.9.9.037_0 < 0.9.9.010_0 yves
On 2007-02-26 21:22:09 -0500, Yves de Champlain wrote:
Hi
I am working on e17 stuff and here is what happened after installing evas 0.9.9.037 while the Portindex refenrence is still at 0.9.9.010 :
Bilbo:~/macports/dports yves$ port outdated The following installed ports are outdated: evas 0.9.9.037_0 < 0.9.9.010_0
BTW, ditto with wormux: wormux 0.8alpha1_0 < 0.7.9_0 -- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
that's most likely caused by epoch (zero by default) $grep wormux PortIndex wormux 1069 variants universal portdir games/wormux description {Wormux is a Worms-clone.} homepage http://www.wormux.org epoch 20070129 platforms darwin name wormux depends_lib {port:libsdl_ttf port:libsdl_image port:libsdl_gfx port:libsdl_mixer port:libsdl_net port:libxmlxx2} maintainers pmq@macports.org long_description {Wormux is free software clone of this game concept. Though currently under heavy development, it is already very playable, with lots of weapons (Dynamite, Baseball Bat, Teleportation, etc.). There are also lots of maps available for your battling pleasure! Wormux takes the genre to the next level, with great customisation options leading to great gameplay. There is a wide selection of teams, from the Aliens to the Chickens. Also, new battlefields can be downloaded from the Internet, making strategy an important part of each battle. Though two human players are currently needed to play (unless you have a split personality :) the creation of artificial players and network play are work-in-progress goals.} categories games version 0.7.9 revision 0 (extract: epoch 20070129) Regards, Elias Pipping On Feb 27, 2007, at 12:11 PM, Vincent Lefevre wrote:
On 2007-02-26 21:22:09 -0500, Yves de Champlain wrote:
Hi
I am working on e17 stuff and here is what happened after installing evas 0.9.9.037 while the Portindex refenrence is still at 0.9.9.010 :
Bilbo:~/macports/dports yves$ port outdated The following installed ports are outdated: evas 0.9.9.037_0 < 0.9.9.010_0
BTW, ditto with wormux:
wormux 0.8alpha1_0 < 0.7.9_0
-- Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/ blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS- Lyon) _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
On Feb 26, 2007, at 10:22 PM, Yves de Champlain wrote:
Hi
I am working on e17 stuff and here is what happened after installing evas 0.9.9.037 while the Portindex refenrence is still at 0.9.9.010 :
Bilbo:~/macports/dports yves$ port outdated The following installed ports are outdated: evas 0.9.9.037_0 < 0.9.9.010_0
yves
Hello Yves! Are you still seeing this behavior? It could be either a bug in Pextlib's rpm-vercomp() function (maybe not properly handling 4-tuple version numbers?) that port(1) calls to perform the actual version comparison between installed and distributed ports (most likely), or a bug in the action_updated proc in port(1) itself that sets up the comparison in the first place (less likely). Please test with 1.4-rc2 sources and if it's still a problem file a ticket about it assigned to the 1.4 milestone, thanks! Regards,... -jmpp
Le 07-03-14 à 19:40, Juan Manuel Palacios a écrit :
On Feb 26, 2007, at 10:22 PM, Yves de Champlain wrote:
Hi
I am working on e17 stuff and here is what happened after installing evas 0.9.9.037 while the Portindex refenrence is still at 0.9.9.010 :
Bilbo:~/macports/dports yves$ port outdated The following installed ports are outdated: evas 0.9.9.037_0 < 0.9.9.010_0
yves
Hello Yves! Are you still seeing this behavior? It could be either a bug in Pextlib's rpm-vercomp() function (maybe not properly handling 4-tuple version numbers?) that port(1) calls to perform the actual version comparison between installed and distributed ports (most likely), or a bug in the action_updated proc in port(1) itself that sets up the comparison in the first place (less likely).
Please test with 1.4-rc2 sources and if it's still a problem file a ticket about it assigned to the 1.4 milestone, thanks!
it was an epoch I had overlooked. thanks yves
participants (4)
-
Elias Pipping
-
Juan Manuel Palacios
-
Vincent Lefevre
-
Yves de Champlain