On Sun, 2009-02-08 at 01:07 -0300, Germán Póo-Caamaño wrote:
> 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.
> > >      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.
> > 
> > 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.
> 
> I wrote a workaround for Debian packages in nautilus extension.
> However, it is not possible to apply the same workaround in RPM packages
> (limitations of RPM) or for installations through setup.py.
> 
> There are two other cases remaining:
>      1. hggtk/shlib.py set THG_ICON_PATH in a non portable way.  I could
>         apply something similar, so it will work for Debian packages.

I assume this could be fixed by creating hggtk/__paths__.py at installer
build time.

>      2. Every text file (such as COPYING.txt) is packages gzipped.

We could use python's zlib library to read the zipped file, if it was
necessary.

> For the second case, I think it doesn't worth the effort to fix it and
> it can wait for the moment.  I would simply remove the menu 'about' from
> the nautilus extension, because currently:
>      1. It pollutes the menu, and nautilus doesn't show the menu in the
>         same order.  So, it looks ugly when 'About' is the first option
>         when the user is expecting to execute an action.
>      2. It is not a killer feature (it is not a feature at all).  The
>         user base may be increased if we provide packages, they can get
>         that information from the download's webpage.  In the future,
>         they can get the information from a stand-alone application
>         and/or from a proper button/menu.

I think you're right for the nautilus extension, though we will probably
want an about command for hgtk.  It could be console based, just dumping
the various versions of mercurial, tortoisehg, etc.

> 
> The repository is located at https://bitbucket.org/gpoo/thg-debian/
> Instructions available in the wiki page and the README file.
> 

Thanks, I'll take a look at this soon.

--
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

Reply via email to