[MacPorts] #57136: py-fabric: would it be possible to maintain a v1 and a v2 version of this port?
MacPorts
noreply at macports.org
Tue Sep 18 07:02:47 UTC 2018
#57136: py-fabric: would it be possible to maintain a v1 and a v2 version of this
port?
------------------------+----------------------
Reporter: hostep | Owner: stromnov
Type: request | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.5.3
Resolution: | Keywords:
Port: py-fabric |
------------------------+----------------------
Changes (by ryandesign):
* status: new => assigned
* cc: stromnov (removed)
* owner: (none) => stromnov
Old description:
> Hi guys!
>
> We are currently using py27-fabric for a couple of scripts to deploy code
> for various (more then 50) projects to a remote server over ssh.
> Our scripts are currently only compatible with the first version of
> Fabric.
> Fabric version 2 is backwards incompatible with version 1:
> http://www.fabfile.org/upgrading.html#upgrading
>
> And Macports recently saw a bump from version 1.14.0 to version 2.3.1 in
> https://github.com/macports/macports-
> ports/commit/469e4413db27d549576b522b8675838d32809d43
> Which I didn't really paid a lot attention to when upgrading all my
> ports, so suddenly my scripts weren't working anymore. I was luckily able
> to revert to the older version using
> https://trac.macports.org/wiki/howto/InstallingOlderPort
> But when for example a new colleague comes into our company and we have
> to setup his development environment, it will be a bit of a hassle to
> install version 1 of Fabric.
>
> Therefore the question: would it be possible to maintain a port for both
> version 1 and version 2 of Fabric, to give people the chance to keep
> running their old scripts, until they've got the chance to upgrade them
> to be compatible with v2 of Fabric.
>
> If this is not technically possible or causes too much hassle, then just
> leave it be.
>
> Thanks!
New description:
Hi guys!
We are currently using py27-fabric for a couple of scripts to deploy code
for various (more then 50) projects to a remote server over ssh.
Our scripts are currently only compatible with the first version of
Fabric.
Fabric version 2 is backwards incompatible with version 1:
http://www.fabfile.org/upgrading.html#upgrading
And Macports recently saw a bump from version 1.14.0 to version 2.3.1 in
[changeset:469e4413db27d549576b522b8675838d32809d43/macports-ports]
Which I didn't really paid a lot attention to when upgrading all my ports,
so suddenly my scripts weren't working anymore. I was luckily able to
revert to the older version using wiki:howto/InstallingOlderPort
But when for example a new colleague comes into our company and we have to
setup his development environment, it will be a bit of a hassle to install
version 1 of Fabric.
Therefore the question: would it be possible to maintain a port for both
version 1 and version 2 of Fabric, to give people the chance to keep
running their old scripts, until they've got the chance to upgrade them to
be compatible with v2 of Fabric.
If this is not technically possible or causes too much hassle, then just
leave it be.
Thanks!
--
--
Ticket URL: <https://trac.macports.org/ticket/57136#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list