Issue 144: Issuese packaging tortoisehg in rpm
http://bitbucket.org/tortoisehg/stable/issue/144/issuese-packaging-tortoisehg-in-rpm
Steve Borho / sborho on Sat, 4 Apr 2009 17:53:20 +0200:
Comment:
Thank for getting the rpm process up and running. Yes, the crew repository
should be your starting point.
I also think that the nautilus extension should probably be a separate package.
I was thinking of two packages:
# hgtk - packages the hggtk python package, hgtk script, and icons
# nautilus-tortoisehg - the shell extension
hgtk should depend on mercurial >= 1.1.2, python >= 2.4, and PyGtk >= 2.10
nautilus-tortoisehg depends on hgtk and nautilus-python
I would be ok with a patch for nautilus-thg.py that removes the environment
variable and hard-coded path hacks since the symlink method works better than
both of them, and we want the installed path to be the default.
For the path problems (icons, COPYING.txt), my thought was for packagers to add
__paths__.py into the hggtk package with path functions for all of these things
which get scattered about. shlib.py and about.py would look for this file
first, then fall back to their original search methods. Something like this:
----
''' __paths__.py '''
get_license_path():
return '/usr/share/doc/tortoisehg-0.7.3/COPYING.txt'
get_icon_path():
return '/usr/share/pixmaps/tortoisehg/icons'
Changes:
status: new -> open
component: nothing -> installer
version: 0.7.3 -> crew
--
This is an issue notification from bitbucket.org.
You are receiving this either because you are the
owner of the issue, or you are following the issue.
------------------------------------------------------------------------------
_______________________________________________
Tortoisehg-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
