[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Duplicity-talk] setup.py patch

From: Kenneth Loafman
Subject: Re: [Duplicity-talk] setup.py patch
Date: Sun, 02 Nov 2008 10:25:51 -0600
User-agent: Thunderbird (X11/20080925)

Michael Terry wrote:
> In hacking on dbus support, I ran into some problems in setup.py.
> Namely, it seems out of date.
> I'm attaching a patch that sort of updates it, but I couldn't get the
> "scripts" line to know that it should rename duplicity-bin to
> duplicity.  So I just had it install duplicity-bin, which doesn't seem
> good.  Maybe someone else can fix that bit?

The script is not meant to be run on the CVS checkout dir, but after
running dist/makedist.py and de-tarring the resultant tar.gz.  The
makedist.py script supplies the correct version to a couple of files
that need to have versioning, one of which is duplicity-bin.

So, the following would be the correct way to handle this:

$ cvs co duplicity
$ cd duplicity/sources
$ dist/makedist.py foo
[makes duplicity-foo.tar.gz]
$ tar xzf duplicity-foo.tar.gz
[makes a duplicity-foo directory]
$ cd duplicity-foo
$ sudo -i
# python setup.py install

Where 'foo' is your version number.

When I make the move to sourceforge.net, I plan to convert to subversion
so that I can make use of the rename features and get the development
structure to match the release structure.  Why CVS still has no rename
is quite is quite beyond me.  Its a royal PITA!


Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]