Samuel Verschelde a écrit :
Le vendredi 1 juillet 2011 01:19:59, Zé a écrit :
2011/6/30 Balcaen John<[email protected]>:
On Thursday 30 June 2011 22:09:15 Zé wrote:
2011/6/29 John Balcaen<[email protected]>:
2011/6/29<[email protected]>:
Revision 115962 Author ze Date 2011-06-29 15:57:57 +0200 (Wed, 29 Jun
2011)
Log Message
- no need to buildrequire and use kde-macros
- use rpm native macros and not variables
[...]
We were using kde4-macros especially because attica is maintained&
requires by KDE, so it's easier to follow it (like a urpmf --requires
kde4-macros Core_Release_SRPMS )
Since attica only needs qt4 theres no need to use kde-macros, thats
why you also have qt cmake macros like %cmake_qt4
I know that it's just using qt4 but we're using kde4 macros as convention
here following our kde's spec layout.
But that layout is to apply for kde packages and for the ones that
require kde, when thats not the case why is there any need to apply
kde macros?
I dont see the point for that.
Same question for me, I maintain qtads which is a qt4 app, but doesn't require
any KDE lib. Is it necessary to use kde-macros for that ?
Samuel
I agree as well.
I've avoided Qt-based packages because of unwanted kde packages being
"required". (Being a Gnome user.)
(Luckily I was able to find non-Qt more-or-less equivalents.)
It seems to me more appropriate to let requires cascade, so as to minimize
installed packages, rather than trying to include (and install) everything.
--
André
