Summary: | graphics/py-sorl-thumbnail: update to 12.4.1 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Kai Knoblich <kai> | ||||||
Component: | Individual Port(s) | Assignee: | Martin Wilke <miwi> | ||||||
Status: | Closed FIXED | ||||||||
Severity: | Affects Only Me | CC: | miwi, ports, python | ||||||
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(ports) |
||||||
Version: | Latest | ||||||||
Hardware: | Any | ||||||||
OS: | Any | ||||||||
Attachments: |
|
Description
Kai Knoblich
2018-05-17 06:42:37 UTC
Comment on attachment 193475 [details]
py-sorl-thumbnail-12.4.1.patch
django metaport prefered
Upstream defaults prefered
Created attachment 193488 [details]
Original patch with minor changes for depends and defaults
Original patch with minor changes for depends and defaults
A commit references this bug: Author: miwi Date: Sat May 26 17:14:21 UTC 2018 New revision: 470901 URL: https://svnweb.freebsd.org/changeset/ports/470901 Log: - Update to 12.4.1 - Changed RUN_DEPENDS (assign to Django 1.11) - Added LICENSE_FILE - Added NO_ARCH - Added DOCS option with the appropriate dependencies - Changed options to reflect the new possibilities with the pluggable engines and key value stores - Updated pkg-descr PR: 228309 Submitted by: freebsd_ports@k-worx.org Approved by: maintainer Sponsored by: iXsystems Inc. Changes: head/graphics/py-sorl-thumbnail/Makefile head/graphics/py-sorl-thumbnail/distinfo head/graphics/py-sorl-thumbnail/files/ head/graphics/py-sorl-thumbnail/files/patch-docs_conf.py head/graphics/py-sorl-thumbnail/pkg-descr I'm struggling to understand how this was committed as "Approved by: maintainer" when the patch I rejected was used in favour of the patch I actually approved. - My patch used the same default image engine as upstream which I believe will cause less confusion for users - May patch used the Django metaport which I believed was best practice for Django dependencies I'd appreciate some clarification on why those choices were ignored. (In reply to Kevin Golding from comment #4) No, using the django metaport is not best practice. (In reply to Antoine Brodin from comment #5) Thanks, I had been under the impression everything was moving to the metaport so it's nice to hear otherwise. I'll phase it out in the future (having been phasing it in). |