On Sat, 2009-02-07 at 13:27 -0600, Steve Borho wrote: > 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.
I wonder why nautilus-thg calls hgtk using Popen and do not import tortoise as a module? I mean, using an API. In this case, it will require only PYTHONPATH to be set properly, which is, IMVHO, easier to get it work than TORTOISEHG_PATH. > > 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. > [...] > > 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. It is a bit different, as far as I can see. I would let it as last resort. However, using run_setup instead of setup is possible to receive an instance of distutils.dist.Distribution, which is useful to ask some of the question I wanted. Unfortunately it is not well documented. Probably useful for Debian-alike packages, but probably not enough for RPM packages. > 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. The installation is useful when you want to enable a package for all users in your systems, also a good setup helps to automatize the build process of packages. It avoids adding extra patches (externals) just for build packages. -- Germán Póo-Caamaño http://www.calcifer.org/ ------------------------------------------------------------------------------ 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
