Package Details: janet-lang 1.36.0-1

Git Clone URL: https://aur.archlinux.org/janet-lang.git (read-only, click to copy)
Package Base: janet-lang
Description: A dynamic Lisp dialect and bytecode vm
Upstream URL: https://janet-lang.org/
Licenses: MIT
Conflicts: janet-lang-git
Provides: janet, jpm
Submitter: GrayJack
Maintainer: psagers
Last Packager: psagers
Votes: 15
Popularity: 0.22
First Submitted: 2019-02-24 02:32 (UTC)
Last Updated: 2024-09-07 22:40 (UTC)

Dependencies (2)

Required by (9)

Sources (3)

Latest Comments

1 2 3 4 5 Next › Last »

psagers commented on 2024-04-27 16:46 (UTC) (edited on 2024-05-12 14:16 (UTC) by psagers)

lto was enabled in the default makepkg.conf last summer.[1] As a consequence, libjanet.a is no longer a native archive and jpm is unable to link to it. The easy fix is to just disable lto:

options=('staticlibs' '!lto')

[1] https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/90bf367e61b4f77f8351d0412be3d0c4ddadb85a

Schnouki commented on 2023-08-17 16:31 (UTC)

Updated and fixed, thanks @Techcable and @jsomedon!

jsomedon commented on 2023-08-04 10:48 (UTC) (edited on 2023-08-04 10:58 (UTC) by jsomedon)

I just checked git version and that package renames default_config to default-config:

install -m644 -T "${srcdir}"/default_config.janet "${pkgdir}"/usr/lib/janet/jpm/default-config.janet

If any of you maintainers could patch this as git version did, that would be awesome.

Techcable commented on 2023-06-27 20:07 (UTC)

Unfortunately I get this problem running jpm on the latest commit:

error: invalid configuration option :cppflags, expected :string-array, got nil
  in errorf [boot.janet] on line 169, column 3
  in load-config [/usr/lib/janet/jpm/config.janet] on line 166, column 7
  in setup [/usr/lib/janet/jpm/cli.janet] on line 62, column 7
  in run [/usr/lib/janet/jpm/cli.janet] (tailcall) on line 84, column 15
  in run-main [boot.janet] on line 3889, column 16
  in cli-main [boot.janet] on line 4042, column 17

I also noticed the path to default_config.janet seems to be wrong. JPM now calls it default-config.janet (notice the dash).

This means when I install the package I get two default config files. One with a dash and one with an underscore.

I don't encounter either of these issues in the janet-lang-git package.

Schnouki commented on 2023-06-02 19:31 (UTC)

Thanks a lot @GrayJack! :)

GrayJack commented on 2023-06-02 18:01 (UTC)

Hey people, I finally had the time to look into this.

I no longer have the time to maintain the package, but I'm looking into how to add Schnouki as a new maintainer.

Schnouki commented on 2023-05-23 13:20 (UTC)

Hey @GrayJack, here's an updated PKGBUILD for 1.28.0: https://paste.sr.ht/~schnouki/eb761726bfb8a0f878d6439a9c47a2958b833147

It's a bit simpler (uses make install as much as possible), uses correct paths for manpages, and doesn't hardcode the jpm commit in the URL, making it a bit easier to update.

Could you please update this package, or add me as a co-maintaner to take care of it?

ruzsa.balazs commented on 2023-05-18 19:20 (UTC)

PKGBUILD copies the man pages to /usr/share/man, I believe they should go to /usr/share/man/man1 instead.

jonathon commented on 2021-09-20 11:22 (UTC)

Checksum update was missed for 1.17.2 (a pain I know well...).

GrayJack commented on 2021-09-19 03:44 (UTC)

@xixixi I think now it works, I'm not sure if any environment variables can change behavior in this case, can you try and report back if everything is working as expected on your end?

1 2 3 4 5 Next › Last »