Re: [aur-general] python-foo and python2-foo - should they conflict?
On 16 October 2012 16:48, Oon-Ee Ng ngoonee.t...@gmail.com wrote: python-foo and python2-foo - should they conflict? Absolutely not. At least, ideally. I may work with both Python versions and in that case will need libraries for each. Shared files have been a problem, and so far the (painful) route is to split them into a -common package (since upstream does not care to handle such inconveniences). See pyqt for an example. -- GPG/PGP ID: C0711BF1
Re: [aur-general] python-foo and python2-foo - should they conflict?
On Tue, Oct 16, 2012 at 5:02 PM, Felix Yan felixonm...@gmail.com wrote: As mentioned in the Arch Packaging Standards [1]: /usr/share/doc/{pkg}Application documentation You should rename the documentation folder of your packages to /usr/share/doc/$pkgname, so there would be not anymore conflict. [1] https://wiki.archlinux.org/index.php/Arch_Packaging_Standards The thing is both use /usr/share/doc/python-foo. Yeah I guess it makes sense that one should use /usr/share/doc/python2-foo, thanks =)