https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227416
--- Comment #13 from Kai <freebsd_po...@k-worx.org> --- (In reply to Kurt Jaeger from comment #12) Thank you very much for the testbuilds, I'm positively surprised because I have not expected that this PR would come so far in such a short time and there's no hurry. A bit work is still needed to do before netbox can be added to the ports tree. An possible approach follows (option A from my initial comment in this PR) for the ports - www/py-django-cors-headers - www/py-django-mptt - www/py-django-js-asset and their respective dependencies that needs to be adjusted/updated. At first here's an overview of the current situation (the dependendies that are not related/bound to Django were left out for the sake of brevity): Dependencies with www/py-django-cors-headers: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For port www/py-django-cors-headers: > www/py-django-annotations (TODO: assign to www/py-django111 and > www/djangorestframework, upstream project seems stale...) > | > +--www/py-django-cors-headers (TODO: assign to www/py-django111) > | > +--www/py-djangorestframework36 > | > +--devel/py-django-rq (TODO: assign to www/py-django111) > | | > | `--www/py-django18 > | > `--devel/py-django-rq-dashboard (TODO: update to 0.3.3) > | > `--devel/py-django-rq Proposed plan for www/py-django-cors-headers (1 or 2 patches) would be roughly: 1. update devel/py-django-rq-dashboard to 0.3.3 (requires maintainer feedback -> swills) 2. - change RUN_DEPENDS of devel/py-django-rq and www/py-django-cors-headers -> www/py-django111 - change RUN_DEPENDS of www/py-django-annotations -> www/py-djangorestframework Dependencies with www/py-django-mptt and www/py-django-js-asset: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ For port www/py-django-cms: > www/py-django-cms (TODO: update to 3.5.2 and assign to www/py-django111) > | > +--www/py-django18 > | > +--www/py-django-classy-tags (TODO: assign to/py-django18) > | | > | `--www/py-django18 > | > +--www/py-django-mptt (TODO: assign to www/py-django111 and > www/py-django-js-asset) > | | > | +--www/py-django18 > | | > | `--www/py-django-js-asset (TODO: assign to www/py-django111) > | | > | `--www/py-django18 > | > | > `--www/py-django-sekizai (TODO: update to 0.10.0 and assign to > www/py-django111) > | > +--devel/py-django18 > | > `--www/py-django-classy-tags (TODO: assign to www/py-django18) > | > `--www/py-django18 For port www/py-django-dpaste: > www/py-django-dpaste (TODO: update to 2.13a and assign to www/py-django111) > | > +--www/py-django18 > | > `--www/py-django-mptt (TODO: assign to www/py-django111 and > www/py-django-js-asset) > | > +--www/py-django18 > | > `--www/py-django-js-asset (TODO: assign to www/py-django111) > | > `--www/py-django18 Proposed plan for www/py-django-cms and www/py-django-dpaste (one whole patch) would be roughly: 1. - update www/py-django-sekizai to 0.10.0 and change RUN_DEPENDS to www/py-django111 (requires maintainer feedback -> xenophon+fbsdpo...@irtnog.org) - change RUN_DEPENDS of www/py-django-classy-tags to www/py-django111 - change RUN_DEPENDS of www/py-django-mptt to www/py-django111 - change RUN_DEPENDS of www/py-django-js-asset to www/py-django111 and www/py-django-mptt - update www/py-django-cms to 3.5.2 and change RUN_DEPENDS to www/py-django111 (requires maintainer feedback -> cs) - update www/py-django-dpaste to 2.13a and change RUN_DEPENDS to www/py-django111 (requires maintainer feedback -> koobs) If the whole approach sounds reasonable for all parties I would create the appropriate patches (and PRs, if required) for it. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
