You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2007-08-15 09:50:29
- dale77
- Member
- From: Down under
- Registered: 2007-02-10
- Posts: 102
- Website
Why was that package updated?
When foo-1.0-4.pkg.tar.gz is released, how do I know what changed from foo-1.0-3?
Is there a simple answer?
Thanks
Dale
Offline
#2 2007-08-15 09:56:04
- AndyRTR
- Developer
- From: Magdeburg/Germany
- Registered: 2005-10-07
- Posts: 1,641
Re: Why was that package updated?
check webcvs
Offline
#3 2007-08-15 10:49:36
- mucknert
- Member
- From: Berlin // Germany
- Registered: 2006-06-27
- Posts: 510
Re: Why was that package updated?
And of course the CHANGELOG upstream.
Todays mistakes are tomorrows catastrophes.
Offline
#4 2007-08-15 11:05:42
- shining
- Pacman Developer
- Registered: 2006-05-10
- Posts: 2,043
Re: Why was that package updated?
And of course the CHANGELOG upstream.
That's rather in the 1.0-3 -> 1.1-1 case 
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
#5 2007-08-15 11:34:28
- mucknert
- Member
- From: Berlin // Germany
- Registered: 2006-06-27
- Posts: 510
Re: Why was that package updated?
Whoops. Sorry. Of course. Ahum. 
Todays mistakes are tomorrows catastrophes.
Offline
#6 2007-08-17 10:07:27
- dale77
- Member
- From: Down under
- Registered: 2007-02-10
- Posts: 102
- Website
Re: Why was that package updated?
I see, so http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/ is my only option?
Perhaps a pacman feature request might be:
root@gordon # pacman -S kernel26
Applied foo patch
etc
Upgrade kernel26? [Y/n]Offline
#7 2007-08-17 11:07:20
- shining
- Pacman Developer
- Registered: 2006-05-10
- Posts: 2,043
Re: Why was that package updated?
I see, so http://cvs.archlinux.org/cgi-bin/viewcvs.cgi/ is my only option?
Perhaps a pacman feature request might be:
root@gordon # pacman -S kernel26 Applied foo patch etc Upgrade kernel26? [Y/n]
pacman has a support for Changelog (-Qc), that you can read after the package has been installed, but no one uses it.
On 608 packages, only 2 have a Changelog : flock and docbook-xml
And only docbook-xml contains real informations.
pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))
Offline
#8 2007-08-17 11:37:10
- dtw
- Forum Fellow
- From: UK
- Registered: 2004-08-03
- Posts: 4,439
- Website
Re: Why was that package updated?
That's not true...I've used it at least 3 times :-P
Offline
#9 2007-08-17 11:42:53
- dale77
- Member
- From: Down under
- Registered: 2007-02-10
- Posts: 102
- Website
Re: Why was that package updated?
pacman has a support for Changelog (-Qc), that you can read after the package has been installed, but no one uses it.
On 608 packages, only 2 have a Changelog : flock and docbook-xmlAnd only docbook-xml contains real informations.
I see, latest is best... What more do I need to know.
Offline
#10 2007-08-17 12:01:00
- Cerebral
- Forum Fellow
- From: Waterloo, ON, CA
- Registered: 2005-04-08
- Posts: 3,108
- Website
Re: Why was that package updated?
pacman has a support for Changelog (-Qc), that you can read after the package has been installed, but no one uses it.
On 608 packages, only 2 have a Changelog : flock and docbook-xmlAnd only docbook-xml contains real informations.
It is important to note that pacman JUST added support for Changelogs, and it was recommended we wait before adding them to package because it was incompatible with pacman 2 (and would result in a .CHANGELOG extracted into the root dir.)
I plan on starting to use them eventually.
Offline
Pages: 1