Page MenuHomeFreeBSD

sysutils/py-ploy_fabric: Apply change to use py-fabric1
AbandonedPublic

Authored by dbaio on Aug 17 2019, 1:33 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Jan 21, 9:18 AM
Unknown Object (File)
Dec 22 2024, 7:12 PM
Unknown Object (File)
Dec 21 2024, 4:23 PM
Unknown Object (File)
Nov 14 2024, 5:13 AM
Unknown Object (File)
Oct 31 2024, 9:33 AM
Unknown Object (File)
Oct 28 2024, 11:48 AM
Unknown Object (File)
Oct 28 2024, 11:42 AM
Unknown Object (File)
Oct 5 2024, 6:45 AM
Subscribers

Details

Reviewers
koobs
Summary
sysutils/py-ploy_fabric: Apply change to use py-fabric1

It's necessary because devel/py-fabric will be updated to v2.5.0 and Fabric 2
is not at 100% feature parity with 1.x! Some features have been explicitly
dropped, but others simply have not been ported over yet.
Test Plan
portlint: OK (looks fine.)
testport: OK (poudriere: 11,12,CURRENT, amd64 and i386, py27)

It was also executed a simple runtime test, checking fabric1 connections

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

koobs requested changes to this revision.EditedAug 23 2019, 6:56 AM

@dbaio Could you combine this and D21304 along with the changes necessary to switch py-fabric to py-fabric1 into a single differential

Also, I think its best to have py-fabric1 just use the main 'fabric' PyPI name and distfiles, but leaving PORTVERSION at the latest 1.x version. This will avoid having to s/fabric/fabric1 all over the codebases of dependent port.

This revision now requires changes to proceed.Aug 23 2019, 6:56 AM