On Monday 16 March 2015 23:16:51 Albert Astals Cid wrote:
We have KPackage depending on kdoctools but since it's optional we pretend
it's not a real dependency and call KPackage tier2
What's in it for us other than lying to ourselves? What's so bad about
KPackage being tier 3?
It'd still
On Tuesday 17 March 2015 08:21:22 Martin Gräßlin wrote:
On Monday 16 March 2015 23:16:51 Albert Astals Cid wrote:
We have KPackage depending on kdoctools but since it's optional we pretend
it's not a real dependency and call KPackage tier2
What's in it for us other than lying to
El Dimarts, 17 de març de 2015, a les 09:16:50, Kevin Ottens va escriure:
On Tuesday 17 March 2015 08:21:22 Martin Gräßlin wrote:
On Monday 16 March 2015 23:16:51 Albert Astals Cid wrote:
We have KPackage depending on kdoctools but since it's optional we
pretend
it's not a real
+1
On Mon, Mar 16, 2015 at 4:16 PM, Albert Astals Cid aa...@kde.org wrote:
We have KPackage depending on kdoctools but since it's optional we pretend
it's not a real dependency and call KPackage tier2
What's in it for us other than lying to ourselves? What's so bad about
KPackage being tier
We have KPackage depending on kdoctools but since it's optional we pretend
it's not a real dependency and call KPackage tier2
What's in it for us other than lying to ourselves? What's so bad about
KPackage being tier 3?
It'd still have only 3 dependencies and be totally usable, no?
Cheers,
