Re: [packages/gnome-themes-standard] Updated to 3.6.1
On 10/17/2012 11:04 PM, megabajt wrote:
%files -f %{name}.lang
%defattr(644,root,root,755)
+%attr(755,root,root) %{_libdir}/gtk-2.0/2.10.0/engines/libadwaita.so
%attr(755,root,root) %{_libdir}/gtk-3.0/3.0.0/theming-engines/libadwaita.so
so, gnome3 core requires gtk+2 and gtk+3 at the same time?
perhaps add subpackages? as ideally gtk+2 is to be gone in gnome3?
--
glen
___
pld-devel-en mailing list
pld-devel-en@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Large patches in git repositories
On Wed, Oct 17, 2012 at 12:02:43PM +0300, Elan Ruusam??e wrote: > also question remains: why not just create new tarball? :) Might be interesting for those reading in Russian: http://www.altlinux.org/Руководство_по_gear (the article looks at several distinct types of package-in-git maintenance) PS: folks, if my references to ALT or pages in Russians hurt anyone's eye please don't hesitate to just tell so; my reason is that some of the pitfalls are known already, and some of them the hard way (it took us ~four years to understand that some RPMs are better maintained as SRPMS even now, for example). -- WBR, Michael Shigorin -- Linux.Kiev http://www.linux.kiev.ua/ ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
Re: Large patches in git repositories
On 17.10.2012 04:36, Kacper Kornet wrote: >with addtional change, that move them to distfiles when you're done Probably it would be best if it was done by developers updating given patch. As they now whether it contains PLD specific changes or not. imho in that case one should create two patches: - one that updates from remote branch, - and the second that applies pld specific changes also question remains: why not just create new tarball? :) -- glen ___ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
