Page MenuHomeFreeBSD

Add FLAVORS to devel/eric6
ClosedPublic

Authored by dbn on Dec 11 2017, 4:02 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Mar 18, 8:04 PM
Unknown Object (File)
Sun, Mar 17, 7:21 AM
Unknown Object (File)
Feb 24 2024, 8:16 AM
Unknown Object (File)
Feb 21 2024, 11:54 PM
Unknown Object (File)
Feb 21 2024, 10:45 PM
Unknown Object (File)
Feb 15 2024, 7:27 PM
Unknown Object (File)
Jan 23 2024, 11:44 PM
Unknown Object (File)
Jan 19 2024, 1:53 AM
Subscribers
None

Details

Summary

Add the following flavor permutations to devel/eric6:

  • Python 2 and Python3
  • Qt 4 and Qt 5

My motivation for switching the port to flavors is:

  1. we are supporting dual major versions of Python and Qt;
  2. given the different versions having user/compile testing is important; and
  3. to allow a package user to not have to use the default version of Python/Qt
Test Plan

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

It would probably be easier to have the flavors named qtX_pyY, so you don't conflict with the flavors from USES=python.

As a side note, is it possible for this port, as it seems to be an IDE, to support both Python versions at the same time ? A bit like editors/vim does.

devel/eric6/Makefile.inc
26–35

This should probably be in the MASTERPORT as it is only used there.

35
​PLIST_FILES= ${DATADIR}/i18n/${PORTNAME}_${I18N_LANG}.qm
40–46

It could be written in an easier way as:

PY_FLAVORS=        py${PYTHON_DEFAULT:S/.//} py${PYTHON2_DEFAULT:S/.//} py${PYTHON3_DEFAULT:S/.//}
​.for flavor in ${PY_FLAVORS}
​.  if empty(FLAVORS:M${flavor}_qt4)
​FLAVORS:=        ${FLAVORS} ${flavor}_qt4 ${flavor}_qt5
​.  endif
​.endfor
49–51

That is not needed.

55–57

I am not sure what this is doing, it is never used. Also, if it is only used in the MASTERPORT, it should probably be in the MASTERPORT.

dbn marked 5 inline comments as done.Dec 12 2017, 6:48 PM
In D13448#281293, @mat wrote:

It would probably be easier to have the flavors named qtX_pyY, so you don't conflict with the flavors from USES=python.

I have switched to the other way around. FYI, I think this is inconsistent with (although a symmetric translation of) the PKGNAMEPREFIX convention.

I suggest python.mk get hardened to avoid this conflict.

As a side note, is it possible for this port, as it seems to be an IDE, to support both Python versions at the same time ? A bit like editors/vim does.

Correct, the IDE does support both python2 and python3 (and thus the flavor is not strictly required) - however I think it will be useful for a package user should they wish to go python3 only.

devel/eric6/Makefile.inc
55–57

It was a carry over from options. It should read RUN_DEPENDS+=...

dbn marked an inline comment as done.
dbn edited the test plan for this revision. (Show Details)

Update patch per comments.

dbn marked an inline comment as done.
dbn added inline comments.
devel/eric6/Makefile.inc
55–57

In this case, PYQRVER is only defined after the includes and so cannot be in MASTERPORT.

In D13448#281425, @dbn wrote:

I suggest python.mk get hardened to avoid this conflict.

Already done.

devel/eric6/Makefile.inc
49–53

USES=python already does that, remove.

55–57

It is defined line 20 of the Makefile.

dbn marked 3 inline comments as done.
dbn edited the test plan for this revision. (Show Details)

Thanks, I has misunderstanding when FLAVOR gets defined (I thought only after including bsd.port.options.mk, or co). Fixed that and removed redundant code.

devel/eric6/Makefile
20–21

FLAVOR can be undefined here, and you are using PYQTVER before it gets defined, so it should be guarded with :U. Also, a default value should probably be set.

devel/eric6/Makefile.inc
60

Is this needed ?

  • Add a default FLAVOR, after defining FLAVORS.
  • Remove redundant ".include <bsd.port.pre.mk>"
dbn marked 2 inline comments as done.Dec 16 2017, 6:22 PM

Is there any other change suggested/required? Can this change be committed (with flavors)?

Let me build test all this, I wonder if there is not some edge case I have not seen but is broken.

I do not think the language files should be flavored. They install the exact same content at the exact same place. The dependencies should probably be reversed, devel/eric6 should depend on them, or they should be pointed out in pkg-message and the dependencies should be removed.

dbn edited the summary of this revision. (Show Details)
dbn edited the test plan for this revision. (Show Details)

I've opted for your second suggest: break dependency of the language ports on eric6 and instead mention them in a pkg-message.

dbn edited the test plan for this revision. (Show Details)

Fix error with i18n ports identified by exp-run. I think this is ready to ship :-)

This revision was not accepted when it landed; it landed in state Needs Review.Jan 10 2018, 6:39 PM
This revision was automatically updated to reflect the committed changes.

@mat thank you for your effort in reviewing this port, and improving both the FLAVORS implementation within eric6 and eric6 in general.