Package Details: fortls 3.1.2-1

Git Clone URL: https://aur.archlinux.org/fortls.git (read-only, click to copy)
Package Base: fortls
Description: A modern Language Server for Fortran.
Upstream URL: https://github.com/gnikit/fortls
Keywords: fortran
Licenses: MIT
Conflicts: fortran-language-server
Provides: fortran-language-server
Submitter: fosskers
Maintainer: fosskers
Last Packager: fosskers
Votes: 4
Popularity: 0.002467
First Submitted: 2022-03-04 08:48 (UTC)
Last Updated: 2024-07-10 02:31 (UTC)

Latest Comments

1 2 3 Next › Last »

fosskers commented on 2024-06-11 08:17 (UTC)

Updated to include to new standards-based build process as suggested by @MarsSeed.

formalincorrect commented on 2024-06-10 07:03 (UTC)

I just tried version 3.1.1 and it seems to be working fine.

fosskers commented on 2024-03-05 23:08 (UTC)

I began to update this but ran into some trouble. I see also that 3.0.0 is coming out soon, so I will complete the migration then.

MarsSeed commented on 2023-11-18 13:25 (UTC)

Thanks! It builds fine for me.

But actually I'm just realizing now that the PKGBUILD should be modernized to avoid executing setup.py directly (also python install complains about this, as this procedure is marked deprecated by upstream since 2021).

Instead, you should follow this (PEP 517 conformant) procedure and see what happens. :)

fosskers commented on 2023-11-18 12:24 (UTC)

Hi @MarsSeed, I've updated the package. Can you verify if the build works for you? It worked for me without adding a patch file, and I get the correct value from fortls --version.

MarsSeed commented on 2023-10-18 11:11 (UTC)

The now merged (but not yet tagged) pull request #330 fixes the setuptools_scm_git_archive issue by removing it from pyproject.toml.

MarsSeed commented on 2023-10-18 10:55 (UTC)

Packaging is now broken because python-setuptools-scm in repo is already at v8.0.4, and the deprecated python-setuptools-scm-git-archive does not work with that.

But as per my verification, fortls' upstream doesn't have any public .git_archival.txt file in their repo root.

Therefore, makedepends=python-setuptools-scm is a drop-in replacement of "setuptools-scm-git-archive", and it is safe to patch pyproject.toml to remove the line referencing the latter.

Please kindly do so, otherwise this package cannot be made via makepkg or devtools. Thank you in advance.

MarsSeed commented on 2023-10-11 13:40 (UTC)

In the meantime, please kindly add depends=('python-packaging). setup.cfg defines it as a runtime dependency (install_requires). Thank you in advance.

MarsSeed commented on 2023-10-11 13:28 (UTC) (edited on 2023-10-11 13:34 (UTC) by MarsSeed)

Scratch that; my assumption was incorrect.

Turns out there is a (simple) migration guide in setuptools_scm_git_archive's README.rst. Devs should check it, and if necessary, implement the outlined change, to ensure compatibility with vanilla setuptools-scm.

MarsSeed commented on 2023-10-11 13:22 (UTC)

Thank you, @fosskers.

AFAIK, upstream also only has to remove "setuptools_scm_git_archive" from pyproject.toml, without any other change. Everything should be working the same with setuptools-scm.

But nevertheless it is the best that you created a GitHub issue, so developers will also be aware of the deprecation, and will have a chance to verify full compatibility with setuptools-scm.

1 2 3 Next › Last »