sort ou pelo sort padrão de qualquer linguagem de progamação, não serve.
terceiro@morere:~/src/noosfero (master)$ git tag
0.1.0
0.10.0
0.10.1
0.10.2
0.10.3
0.11.0
0.11.1
0.11.2
0.11.3
0.11.4
0.11.5
0.12.0
0.2.0
0.3.1
0.4.0
0.5.0
0.6.0
0.7.0
0.8.0
0.9.0
terceiro@morere:~/src/noosfero (master)$ git tag | sort
0.1.0
0.10.0
0.10.1
0.10.2
0.10.3
0.11.0
0.11.1
0.11.2
0.11.3
0.11.4
0.11.5
0.12.0
0.2.0
0.3.1
0.4.0
0.5.0
0.6.0
0.7.0
0.8.0
0.9.0
O script a seguir resolve meu caso:
#!/usr/bin/ruby
out = $stdin.readlines.map { |s| s.strip }.sort do |v1,v2|
(v1 == v2) ? 0 : (system("dpkg --compare-versions #{v1} le #{v2}") ? -1 : 1)
end
puts out
Salvei ele em ~/bin/version-sort e fix um chmod +x ~/bin/version-sort.
Aí eu consigo fazer coisas assim:
terceiro@morere:~/src/noosfero (master)$ git tag | version-sort
0.1.0
0.2.0
0.3.1
0.4.0
0.5.0
0.6.0
0.7.0
0.8.0
0.9.0
0.10.0
0.10.1
0.10.2
0.10.3
0.11.0
0.11.1
0.11.2
0.11.3
0.11.4
0.11.5
0.12.0
UPDATE: Pedro me indicou por e-mail uma alternativa usando opções do próprio sort:
terceiro@morere:~/src/noosfero (master)$ git tag | sort -n -t . -k 1,1 -k 2,2 -k 3,3
0.1.0
0.2.0
0.3.1
0.4.0
0.5.0
0.6.0
0.7.0
0.8.0
0.9.0
0.10.0
0.10.1
0.10.2
0.10.3
0.11.0
0.11.1
0.11.2
0.11.3
0.11.4
0.11.5
0.12.0
De fato pra esse caso específico funciona que é uma beleza, e é simples fazer uma alias do shell com o comando todo. Mesmo assim essa abordagem usando o dpkg --compare-version tem a vantagem de ser genérica: eu posso abstrair o formato do número de versão que o dpkg se vira: x.y.z, x.y, x.y.z.w, x:y.z, etc.
]]>
]]>
The charter of the project is now broadened because of the tremendous need of enterprises to go to the next level in collaboration. The major areas of focus are:
Then the new project was born, with a work name of "Nextwiki", which had to be changed ASAP because "TWiki" is a registered trademark of Peter Thoeny, and he demanded that the new project don't use anything that looks like "TWiki". The things are running as fast as possible, and today it was announced the new name: Foswiki. The process for choosing the new name was very democratic and was supported by a professional copywriter. The donain name for the new name is already set up.
There is a more detailed explanation of the whole process that led to the fork. Actually it's not a fork, since all relevant people that were involved in TWiki development are now involved with Foswiki development. It's the same project, now with a different name because of a trademark issues.
On the TWiki side, things seem to be not good at all. The development mailing list traffic in the last two weeks is composed almos 100% by failing unit tests messages sent automatically by the -- now probably unatended -- integration server), which looks to me as a sad, silent and unnecessary death. Too bad.
Former TWiki users are invited to migrate to Foswiki as soon as there is a first release, which will mainly include a rebranding (i.e. removing all mentions to "TWiki"). FOSWIki will be able to deal with all your current content in TWiki and will evolve much more vividly than ever before, without breaking your content and applications.
Long life to Foswiki.
UPDATE: the Right Way to capitalize is "Foswiki". This is interesting because people always capitalized TWiki wrong, so ... we are not repeating the mistakes from the past. 
]]>
