> Also, changing -devel right now at the same will cause all sorts of
> support issues as people deal with the migration - not everyone reads
> the UPDATING file before issuing "portupgrade -a".
Even a solution should be to mark the haproxy-devel has "Moved" (see
/usr/ports/MOVED)
I see in portup
AH>> However, the way I think it should go in the ideal situation, is that
AH>> the haproxy port should contain the latest and greatest stable release
AH>> (1.4.x), and the haproxy-devel port should go to the latest experimental
AH>> snapshot.. If you think keeping a 1.3.x tree alive is usefull (wh
2 matches
Mail list logo
