Arch Linux User Repository

@SpieringsAE I added it without bumping pkgver and pkgrel!

for the next version, the riscv64 arch can be added, just tested it on my jh7110 based system, thanks in advance!

...files you mention are currently not part of the meson build configuration

You are technically correct, and I understand your point. The default meson ... install ... build does what it does and it does not do more. Because the developer didnt tell it to do "more".

So he is the absolute master of THAT build recipe, the meson build one. However he is not absolute master dictacting what THIS build recipe, the PKGBUILD here on the AUR, should do.

There is no stone tablet written rule, preventing you, the PKGBUILD maintainer, of doing what you decide to do with your cooking recipe. You dont have to "wait" for the developer to stuff more in his cooking recipe.

You have a tar.gz containing all you need. A dead simple extra line "install -Dm644 ...WHATEVER-I-WANT... .../usr/share/...TO-WHEREEVER-I-WANT... is enough.

As many many other PKGBUILD maintainers do.

I didnt dream this as some kind of exotic personal child request last night. And I wouldnt be here asking for it if I hadnt seen it as common practice elsewhere.

... I don't think the NEWS, TODO and README.md is that helpful 

Could not disagree more. Specially the NEWS file. Essential to keep up with things in a not so old tool, still being subject to many changes. And dealing with attached hardware.

@m040601 the examples dir and other files you mention are currently not part of the meson build configuration. If you think it is a bug I guess it is better to fix it upstream, but I don't think the NEWS, TODO and README.md is that helpful in an install. Maybe the examples are good to have. I suggest you report an upstream issue to add it as an option.

the released tar.xz contains:

......
tio-3.7/NEWS
tio-3.7/README.md
tio-3.7/TODO
tio-3.7/examples/
tio-3.7/examples/config/...
tio-3.7/examples/lua/...
......

Please make sure these files end up in

/usr/share/doc/tio/

It appears that pkgconf is now needed for the build process to be able to find lua. When building in a clean chroot in x86 Arch Linux, interestingly I already have pkgconfig installed. However, I got the following error building on a similar aarch64 (arm) chroot today:

Did not find pkg-config by name 'pkg-config'
Found pkg-config: NO
Did not find CMake 'cmake'
Found CMake: NO
Run-time dependency lua-5.4 found: NO (tried pkgconfig and cmake)
Run-time dependency lua-5.3 found: NO (tried pkgconfig and cmake)
Run-time dependency lua-5.2 found: NO (tried pkgconfig and cmake)
Run-time dependency lua-5.1 found: NO (tried pkgconfig and cmake)
Run-time dependency lua found: NO (tried pkgconfig and cmake)

src/meson.build:34:2: ERROR: Problem encountered: Lua could not be found!

Since lua is a dependency already of tio, and there was discussion here previously about cmake not being required, I tried to add pkgconf as a dependency and that works fine.

I did search the upstream repo for any indication that this is indeed required and admit I could find none... But it is obviously using pkconfig or cmake to find its dependency, lua.

Thanks for the work maintaining this very usefull PKGBUILD. If everyone votes for it, maybe one day could be an official Arch package.

Here are some issues that still need to be polished in this PKGBUILD. Some were already mentioned in the previous comments. Please read them and pay attention. If you need help, just ask.

POINT NR.1: unnecessary dependencies

Dependencies (5)
  • bash-completion (bash-completion-git^AUR)

10 depends=('glibc' 'libinih' 'bash-completion' 'lua')

You dont have to and should not force the "bash-completion" official package as a dependency. This was already mentioned earlier.

Sacro commented on 2023-08-06 13:12 (UTC)
Please don't depend on bash-completion, not everyone has or uses bash.
Also no need to depend on glibc, it's part of the base system.

Perhaps you are confusing "bash-completion" the package, that is the tool or machinery, with the location,

/usr/share/bash-completion/completions/

Do

pacman -Qo usr/share/bash-completion/completions/

to see who "owns" it.

And thats the only thing you need to take care. That a folder "/usr/share/bash-completion/completions" exists (which is true in 99.99 %) of all Arch systems. And that you put the file "tio" there.

This is usually a simple copy operation with "install", something like

  install -Dm644 "${_output}/bash" "${pkgdir}/usr/share/bash-completion/completions/XXXXX "

I dont know how "meson" works,

22   cd "$srcdir/$pkgname-$pkgver"
23   meson install -C build --destdir "$pkgdir"

But if you need help, just ask and somebody will help you.

In any case remember that you are not supposed to follow blindly the developers Makefile, or meson, or installation instructions. They are general Linux installation procedures. They are to be adapted to the Archlinux guidelines if and when necessary.

POINT NR. 2 - Readme, NEWS, and examples

This is the only thing that this PKGBUILD currently stuffs in the user system.

$ pacman -Ql tio

tio /usr/bin/tio
tio /usr/share/bash-completion/completions/tio
tio /usr/share/man/man1/tio.1.gz

However,

$ wget https://github.com/tio/tio/releases/download/v2.8/tio-2.8.tar.xz

$ tar tf tio-2.8.tar.xz

......
......
tio-2.8/NEWS
tio-2.8/README.md
tio-2.8/example/
tio-2.8/example/config
tio-2.8/example/control-lines-test.lua
......
......


Those files are usefull to have on the system. That NEWS file is super
important and well written to keep up with things and changes. There is no
reason for them to go to the trash. They should end up in something like,

/usr/share/doc/tio/README.md /usr/share/doc/tio/NEWS /usr/share/doc/tio/example/...

Again a simple copy operation like for ex,

  install -Dm644 "XYZ..." "${pkgdir}/usr/share/doc/tio/XYZ..."

POINT NR3: URL

As already mentioned, it is not,

 Upstream URL:   http://tio.github.io/

It is https://tio.github.io/

Or, in my opinion better, https://github.com/tio/tio since there is nothing to see in the "github.io" page.

Thanks in advance.

Thanks for reporting @ocelotsloth.

GPL-2.0-or-later change from GPL-2.0-only happened on 3f29bce (Apr 24, 2016. First tagged in v1.3)

The license in this package isn't quite correct. It should be the SPDX identifier GPL-2.0-or-later https://github.com/tio/tio/blob/master/LICENSE

Upstream URL:   http://tio.github.io/

Should be corrected. Both 'http' to https' now redirect to 'https://github.com/tio/tio'