Bug#519972: git-cola: should use private module dirs.

2009-04-20 Thread David Aguilar
On 0, Bernd Zeimetz wrote: > Package: git-cola > Version: 1.3.5.28-1 > Severity: serious > > git-cola ships private modules, they should be installed to > /usr/share/git-cola > according to the policy [1], if there is not a good reason to install them > system-wide. As the modules are not used

Bug#519972: git-cola: should use private module dirs.

2009-03-17 Thread David Aguilar
On 0, Bernd Zeimetz wrote: > David Aguilar wrote: > > > > Thanks Bernd. > > What should I do about the .pyc/.pyo files? > > > > I'm assuming that I shouldn't generate them and should instead > > let Debian generate them? > > Right, that's what python-support (and python-central, if you like th

Bug#519972: git-cola: should use private module dirs.

2009-03-17 Thread Bernd Zeimetz
David Aguilar wrote: > > Thanks Bernd. > What should I do about the .pyc/.pyo files? > > I'm assuming that I shouldn't generate them and should instead > let Debian generate them? Right, that's what python-support (and python-central, if you like that more) takes care of. They'll also take care

Bug#519972: git-cola: should use private module dirs.

2009-03-16 Thread David Aguilar
On Mon, Mar 16, 2009 at 7:25 AM, Bernd Zeimetz wrote: > Package: git-cola > Version: 1.3.5.28-1 > Severity: serious > > git-cola ships private modules, they should be installed to > /usr/share/git-cola > according to the policy [1], if there is not a good reason to install them > system-wide. As

Bug#519972: git-cola: should use private module dirs.

2009-03-16 Thread Bernd Zeimetz
Package: git-cola Version: 1.3.5.28-1 Severity: serious git-cola ships private modules, they should be installed to /usr/share/git-cola according to the policy [1], if there is not a good reason to install them system-wide. As the modules are not used by any other program, they should be moved int