[MacPorts] #62557: port is 4 months stale compared to nightly unstable version of gimp, is missing important GIMP commits

[MacPorts]

#62557: port is 4 months stale compared to nightly unstable version of gimp, is
missing important GIMP commits
--------------------------+--------------------
  Reporter:  bootchk      |      Owner:  (none)
      Type:  enhancement  |     Status:  new
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:
Resolution:               |   Keywords:
      Port:  gimp2-devel  |
--------------------------+--------------------
Description changed by bootchk:

Old description:

> The port uses a commit that is four months old.   Even at the time the
> port was created, it was only about a month newer than the stable version
> port (gimp2).  With the passage of time, the gimp2-devel port
> increasingly does not represent the current state of the development
> version of GIMP 2.10.
>
> Maybe it is just a matter of education, or that I missed reading
> something.   I assumed that the port would pull the latest, nightly
> version, whenever the port was built.  Maybe I am supposed to edit the
> port file myself, to change the pulled version.  Maybe you could put a
> comment in the port file, or in the documentation for Macports explaining
> the purpose of ports with the "-devel" nomenclature.  I suppose if a port
> file pulled the latest commit every time it was built, it would be nearly
> impossible to keep track of defects.
>
> (Also, when I browsed Macports, the "devel" category, it did not seem to
> find gimp2-devel.)
>
> Related to another issue that I will create a ticket for, the "gimp2"
> port is missing a patch for "unable to open script-fu-int".
>
> Just to explain the context, when I first used the gimp2 port, I found
> that issue.  So I thought, "get the gimp2-devel port, it will have all
> the latest GIMP commits."  But it doesn't, and I later found that there
> is a commit in GIMP that fixes the issue.
>
> Thanks for your work, I really like Macports, I am not trying to be
> critical, just to document.

New description:

 The port uses a commit that is four months old.   Even at the time the
 port was created, it was only about a month newer than the stable version
 port (gimp2).  With the passage of time, the gimp2-devel port increasingly
 does not represent the current state of the development version of GIMP
 2.10.

 Maybe it is just a matter of education, or that I missed reading
 something.   I assumed that the port would pull the latest, nightly
 version, whenever the port was built.  Maybe I am supposed to edit the
 port file myself, to change the pulled version.  Maybe you could put a
 comment in the port file, or in the documentation for Macports explaining
 the purpose of ports with the "-devel" nomenclature.  I suppose if a port
 file pulled the latest commit every time it was built, it would be nearly
 impossible to keep track of defects.

 (Also, when I browsed Macports, the "devel" category, it did not seem to
 find gimp2-devel.)

 Related to Macports issue #61799 that I just commented on.

 Just to explain the context, when I first used the gimp2 port, I found
 that issue.  So I thought, "get the gimp2-devel port, it will have all the
 latest GIMP commits."  But it doesn't, and I later found that there is a
 commit in GIMP that fixes the issue.

 Thanks for your work, I really like Macports, I am not trying to be
 critical, just to document.

--

-- 
Ticket URL: <https://trac.macports.org/ticket/62557#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS