Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 11 Dec 2017 11:34:01 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 224242] Some FLAVOR related changes
Message-ID:  <bug-224242-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224242

            Bug ID: 224242
           Summary: Some FLAVOR related changes
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Ports Framework
          Assignee: portmgr@FreeBSD.org
          Reporter: FreeBSD@ShaneWare.Biz
                CC: freebsd-ports-bugs@FreeBSD.org

After the FLAVOR change I think there are a couple of things that still nee=
d to
be addressed that affect concurrent python port installs. As package repos =
now
have two flavours for many python ports, trying to install one using the pkg
origin will break the install due to conflicts.

1. USE_PYTHON=3Dconcurrent should be considered a default option, or part of
implementing flavour, maybe have noconcurrent if a port specifically doesn't
need it.

2. Using concurrent still has an issue of conflicting man pages, see bug
#220214 as a possibile solution for this.

3. If a port is python3 only then no default scripts exist, only the versio=
ned
script is created. See bug #216479.

4. Would it be possible for pkg to record the package flavour so that it ca=
n be
queried? Maybe even a config option to control what flavours it will instal=
l?

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224242-13>