glom: update to 1.26.0

[ryandesign (Ryan Carsten Schmidt)]

​glom 1.26.0 is available; perhaps the port should be updated to this version.

[l@…]

Cc Me!

[moilejter@…]

After downloading the current source to glom (1.22.0), the attempt to configure it complained above other packages being missing:

  No package 'pygobject-3.0' found
  No package 'libgdamm-5.0' found
  No package 'libgda-5.0' found
  No package 'libgda-postgres-5.0' found
  Requested 'libepc-1.0 >= 0.4.0' but version of Easy Publish and Consume Library is 0.3.11

(the last one is available in macports, but as an older version...).

I can download the others, too, and install manually... But what is the procedure to volunteer some of these into macports?

[moilejter@…]

Cc Me!

[grahamperrin@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

Replying to moilejter@…:

I can download the others, too, and install manually... But what is the procedure to volunteer some of these into macports?

File new port tickets. Attach portfiles. Or, for existing ports you want to update, file port update tickets and attach unified diffs of the portfiles.

[dbevans (David B. Evans)]

Replying to moilejter@…:

After downloading the current source to glom (1.22.0), the attempt to configure it complained above other packages being missing:

  No package 'pygobject-3.0' found
  No package 'libgdamm-5.0' found
  No package 'libgda-5.0' found
  No package 'libgda-postgres-5.0' found
  Requested 'libepc-1.0 >= 0.4.0' but version of Easy Publish and Consume Library is 0.3.11

(the last one is available in macports, but as an older version...).

All of these dependencies are now available in Macports at the correct version levels.

[dbevans (David B. Evans)]

glom stable version 1.26.0 is now available.

[dbevans (David B. Evans)]

Attached is a patch that takes a first shot at updating glom to version 1.26.0. It builds successfully for me but there are still some runtime issues that need to be fixed before committing. The first and most prominent is that glom crashes on launch when using the default locale. I haven't been able to understand what is happening here so I'm presenting it as is. To get around this problem you can start the program as follows:

LANG=C glom

Hopefully someone else will be able to help with a solution.

[dbevans (David B. Evans)]

Work in progress patch to update to version 1.26.0.

[ryandesign (Ryan Carsten Schmidt)]

Has duplicate #44591.

No reason to wait to commit this, really, since the current port has a nonexistent dependency (#35102) thus cannot possibly be working any better.

[dbevans (David B. Evans)]

As with other GNOME ports, version 1.26.0 is the current stable release, 1.27.1 is the current unstable release.

I agree that committing this will give us a version that at least builds and can be run with some caveats. I was hoping to get some feedback from Landon on this but, failing that, I suggest adding openmaintainer so that the known issues can be worked on more freely.

[dbevans (David B. Evans)]

Updated to version 1.26.0, openmaintainer in r123543 (maintainer timeout). Notes added to address known locale problem.

[m.rick@…]

Replying to devans@…:

Updated to version 1.26.0, openmaintainer in r123543 (maintainer timeout). Notes added to address known locale problem.

Thank you very much for your work. it is better with some caveats that can be tricked than nothing, making a startup script with LANG=C glom that's not big deal.