On Sat, 2009-02-07 at 11:23 -0300, Germán Póo-Caamaño wrote: > On Fri, 2009-02-06 at 23:16 -0600, Steve Borho wrote: > > On Fri, 2009-02-06 at 23:35 -0300, Germán Póo-Caamaño wrote: > > > # HG changeset patch > > > # User Germán Póo-Caamaño <[email protected]> > > > # Date 1233974039 10800 > > > # Node ID cc127a67a83c2c27015693977208751b5c2a750f > > > # Parent 11b2b0c0302705e1a0ee856998a4aa2b21a198bb > > > setup: enable installation on posix systems. > > > > Pushed, thanks. > > > > Would you be interested in figuring out what we need to do to make > > binary packages on Linux for tortoisehg and it's nautilus integration? > > Well, there are some issues, mainly related with the fact that packages > must be relocatable. > > To be known: > 1. The license text should installed under usr/share (please note > that I it is usr/share not /usr/share), so the about dialog > fails because it tries to read it from the root of tortoisehg > using: (os.path.join(prog_root, "COPYING.txt")). When I > converted some dialogs to XML (libglade or GtkBuilder) this > wasn't an issue anymore because it was included in the XML file, > however I was told an XML file was not an option. > 2. The nautilus extension depends on TORTOISEHG_PATH, but we don't > know the PATH where tortoisehg will be installed. > 3. A similar issue will happen with icons for Nautilus extension. > 4. I haven't seen if the generated file for version will be an > issue yet. > > For instance, the package must allow to run commands like: > > $ python setup.py install --home > > or > > $ python setup.py install --root=/usr/local > > or any other combination different than the usual. Hardcoding the PATH > because we could expect them to be installed under / is ugly and it > won't be accepted in downstream. > > I don't know how to get the prefix or base install directory used when > setup.py is ran. One possible workaround could writing that path in a > file and to be read in runtime by the application. > > Packages that uses easy_install, includes all files inside a same root > (like the used currently), but I don't how it works for win-nt > installations. > > On the other hand, these must separated in two packages: the nautilus > extension and tortoisehg itself. Some users doesn't use nautilus, but > still they would like to use hgtk. > > Some time ago I built them using the work started by Peter Arrenbrecht, > you can find them at https://launchpad.net/~gpoo/+archive/ppa > > I didn't make any advance before getting the setup patch accepted, but I > do remember the issues :-)
Have you looked at hgview's setup.py? They seem to be further along in tackling this issue. I'm thinking of having setup.py generate a __paths__.py file just like it generates a __version__.py. Though both of those files should live under hggtk so they they can be found easily. There's no need to install the tortoise/ package on posix systems. As near as I can tell, setup.py in the tortoisehg sources is only used on Windows to build the standalone installer, of which none have ever been released. -- Steve ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
