Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Apr 2020 21:06:58 +0000
From:      bugzilla-noreply@freebsd.org
To:        gnome@FreeBSD.org
Subject:   [Bug 245519] graphics/gimp: relies on graphics/py-gimp and Python 2.7
Message-ID:  <bug-245519-6497@https.bugs.freebsd.org/bugzilla/>

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

            Bug ID: 245519
           Summary: graphics/gimp: relies on graphics/py-gimp and Python
                    2.7
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: gnome@FreeBSD.org
          Reporter: andymenderunix@gmail.com
             Flags: maintainer-feedback?(gnome@FreeBSD.org)
          Assignee: gnome@FreeBSD.org

graphics/gimp has Python support ON by default. This pulls in graphics/py-g=
imp
which is a rather old port and requires Python 2.7 explicitly. From the
Makefile for graphics/py-gimp:
DEPRECATED=3D     Uses deprecated version of python
EXPIRATION_DATE=3D        2020-08-15

GIMP_SLAVE=3D     pygimp

USES=3D           python:2.7
USE_GNOME=3D      pygtk2

The Fedora community has a similar problem, just before their 32 release:
https://bugzilla.redhat.com/show_bug.cgi?id=3D1737933

GIMP3 is in the making and it *should* default to Python3, however no info =
is
available on the official Roadmap: https://wiki.gimp.org/wiki/Roadmap#GIMP_=
3.0

I can start tinkering with GIMP3 to see whether it's possible to re-use the
current Makefile, but that would still provide a "gimp-devel" port at best.

The alternative would be to disable Python support in graphics/gimp so that=
 the
port continues building past its expiration date.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



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