[Mageia-dev] [RPM] cauldron core/release kphotoalbum-0-1.mga2
pasotti.matteo at gmail.com
Sat Sep 10 03:14:36 CEST 2011
-----BEGIN PGP SIGNED MESSAGE-----
Il 10/09/2011 02:22, Balcaen John ha scritto:
> Le Vendredi 9 Septembre 2011 23:42:46 Florian Hubold a écrit :
>>> like %_kde_applicationsdir or %_kde_appsdir
>>> Regarding the %mkrel if you're using a git tarball it could be
>>> nice to have it announced in the file name
>>> something for release like %mkrel -c git %git should do the trick
>> Interesting. What does %mkrel -c git do?
> It's interressing for git/svn snapshot so you can get a srpm like this
> for exemple :
> version here is 1.0 & the Release is set to %mkrel -c git %gitdate
>> Isn't there a problem when using git commit hashes as they are random,
>> unsorted, and shouldn't be used in a version comparison?
> Yep i forgot to mention that it's better to use the date of the snapshot
> instead of the commit hash (which can still be available somewhere in
> the spec for memory).
>> See f.ex. this thread:
>> Although i didn't look at the SPEC at all ...
> No you're right, the %git macro here is not correct :p
the archive of the sources of the latest "stable" release (4.1.1) it's
not available on the web site (404 error). Moreover the one coming
from the git repo don't compile due to an error related to exiv2 (I'm
always talking about the 4.1.1 version).
That's why I choose the latest git revision (cloned the 2011.09.09) to
build the package. This revision compiles and works fine but it doesn't
match version 4.1.1 (the application itself displays "Version GIT" into
the about box) so I've used that version numbering to allow future upgrades.
Let me know if you think it's an acceptable behaviour, please.
I'm fixing the spec right now, thank you for your support and your
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mageia - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----
More information about the Mageia-dev