You are not logged in.
- Topics: Active | Unanswered
#1 2012-01-23 12:41:07
- nasosnik
- Member
- From: Athens - Greece
- Registered: 2011-03-10
- Posts: 27
Different sizes and MD5sums at package from the same PKGBUILD
I have noticed that if i build a package from a given PKGBUILD with makepkg, two or more times, the resulting .pkg.tar.xz 's have different sizes and of course different MD5sum 's.
For example i have built rxvt-unicode from abs/extra two times and the resulting packages where 551,580 Bytes the first and 553,824 Bytes the second time.
How is that possible to happen?
Offline
#2 2012-01-23 13:14:51
- karol
- Archivist
- Registered: 2009-05-06
- Posts: 25,440
Re: Different sizes and MD5sums at package from the same PKGBUILD
It gets the sources from github, so maybe something changed in between these two builds.
Offline
#3 2012-01-23 13:48:55
- nasosnik
- Member
- From: Athens - Greece
- Registered: 2011-03-10
- Posts: 27
Re: Different sizes and MD5sums at package from the same PKGBUILD
It gets the sources from github, so maybe something changed in between these two builds.
The same is happening for any package i build. If i build it 5 times, i get 5 different sizes.
Offline
#4 2012-01-24 06:31:57
- Snowman
- Developer/Forum Fellow
- From: Montreal, Canada
- Registered: 2004-08-20
- Posts: 5,212
Re: Different sizes and MD5sums at package from the same PKGBUILD
The build date gets included in the package meta data and in some case in the binaries as well. That is why the md5sums are different and it's probably the cause of the difference in size too.
Offline