rdiff-backup-users
[Top][All Lists]
Advanced

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

Re: [rdiff-backup-users] RPM, #!/usr/bin/python -> #!/usr/bin/python2.2


From: Ben Escoto
Subject: Re: [rdiff-backup-users] RPM, #!/usr/bin/python -> #!/usr/bin/python2.2
Date: Wed, 12 Nov 2003 01:56:26 -0800

On 12 Nov 2003 09:11:38 +0100 Erik Forsberg <address@hidden> wrote:
> I think the hashbang of the rdiff-backup "executable" should be
> changed from "#!/usr/bin/python" to "#!/usr/bin/python2.2", at least
> in the version that comes with the RPM package.

If you install from source the setup script will automatically munge
the rdiff-backup executable so that the "#!" line points to the right
python binary.

This seems like the right behavior, so the actual #! line in the
binary RPMs are determined by the machine they are built on.
"/usr/bin/python2.2" isn't that great a choice anyway, now that people
are upgrading to 2.3.

The main problem now is that the current source RPMs will not notice
if python 2.x is called "python2".  The old rdiff-backup source RPM's
would autodetect this and build with the right dependencies and
everything.  See for instance the version at:

http://savannah.nongnu.org/cgi-bin/viewcvs/rdiff-backup/rdiff-backup/dist/rdiff-backup.spec.template?rev=1.1.2.3&content-type=text/vnd.viewcvs-markup

Somehow this functionality has been lost though.


-- 
Ben Escoto

Attachment: pgpQK1zI6sxo2.pgp
Description: PGP signature


reply via email to

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