Package Details: ov-bin 0.50.2-1

Git Clone URL: https://aur.archlinux.org/ov-bin.git (read-only, click to copy)
Package Base: ov-bin
Description: Feature-rich terminal-based text viewer. It is a so-called terminal pager.
Upstream URL: https://github.com/noborus/ov
Keywords: less more ov tail
Licenses: MIT
Conflicts: ov
Provides: ov
Submitter: JulianXhokaxhiu
Maintainer: JulianXhokaxhiu
Last Packager: JulianXhokaxhiu
Votes: 9
Popularity: 0.74
First Submitted: 2023-01-04 09:02 (UTC)
Last Updated: 2025-12-06 13:43 (UTC)

Dependencies (2)

Required by (1)

Sources (3)

Latest Comments

1 2 Next › Last »

JulianXhokaxhiu commented on 2025-11-23 11:02 (UTC)

Done, thanks for the suggestion

ChongChengAC commented on 2025-11-18 09:53 (UTC)

please add xclip to (optional) dependency. because without it, you can't copy text from ov.

README.md:

Copying to the clipboard uses atotto/clipboard. For this reason, the 'xclip' or 'xsel' command is required in Linux/Unix environments.

[ctrl+c] * copy to clipboard

JulianXhokaxhiu commented on 2025-03-02 10:53 (UTC)

Thanks @m040601 for the suggestions. Pushed an updated revision with the new changes in place. Cheers!

kseistrup commented on 2025-03-02 10:50 (UTC)

@m040601

ArchWiki's package guidelaines beg to differ: https://wiki.archlinux.org/title/Arch_package_guidelines#Directories

I'm not worried about conflicts here, for me it's about being able to locate the relevant files — say licenses and docs — easily.

The PKGBUILD specification says explicitly aboout the license: “The corresponding license text must be placed in directory /usr/share/licenses/pkgname”. See https://wiki.archlinux.org/title/PKGBUILD#license It would be very illogical to use another naming for documentation.

m040601 commented on 2025-03-02 10:38 (UTC) (edited on 2025-03-02 10:46 (UTC) by m040601) 

Shouldn't the doc directory be /usr/share/doc/$pkgname/?

You mean like, 

/usr/share/doc/ov-bin/...
/usr/share/doc/ov-git/...
/usr/share/license/ov-git/...
/usr/share/license/ov-bin/...

Nooooooo. Never ... That would be a mess.

The directories are called "ov". Whether the PKGBUILD is called "ov-git" or "ov-bin" or "ov-strawberries", or "ov-bananas". Period.

You dont need to "worry" about conflicts. You, the AUR user, chooses one "ov" from the AUR. The "ov", "ov-bin" or "ov-git". You can only have one at the same time installed on your computer.

That is the job for these kind of tags,

   Conflicts:    ov
   Provides:     ov
   ...
   (Replaces xyz ... etc)

That should be used by the "-git" and "-bin" versions of the PKGBUILDs.

kseistrup commented on 2025-03-02 08:40 (UTC)

@m040601

Shouldn't the doc directory be /usr/share/doc/$pkgname/?

/usr/share/doc/ov-bin/ov.yaml
/usr/share/doc/ov-bin/ov-less.yaml

I have implemented your $pkgname.install file in thje ov-git package. Thanks.

m040601 commented on 2025-03-01 23:58 (UTC) (edited on 2025-03-02 00:01 (UTC) by m040601)

pacman -Ql ov-bin

ov-bin /usr/bin/ov
ov-bin /usr/share/doc/ov/README.md
ov-bin /usr/share/licenses/ov/LICENSE
...
ov-bin /usr/share/ov/ov-less.yaml
ov-bin /usr/share/ov/ov.yaml
...

For consistency. It is better to install those "ov.yaml" files in the "doc" folder, "/usr/share/doc/..." . Not in "/usr/share/ov".

This, 

ov-bin /usr/share/doc/ov/ov-less.yaml
ov-bin /usr/share/doc/ov/ov.yaml

Not this, 

ov-bin /usr/share/ov/ov-less.yaml
ov-bin /usr/share/ov/ov.yaml

That is what the others do both,

It would be nice if the maintainers of the 3 different PKGBUILD "ov", "ov-git", "ov-bin" maintainers, cooperate, collaborate or at least check each other for consistency. And to avoid repeating work.

m040601 commented on 2025-03-01 23:36 (UTC) (edited on 2025-03-01 23:47 (UTC) by m040601)

```` post_install() { # Hint user about ov config file echo ">> ov provides two example config files (ov.yaml, ov-less.yaml) but none of them are echo ">> You can find them here '/usr/share/ov' and here is an example of how to use the de echo ">> $ cp /usr/share/ov/ov.yaml ~/.ov.yaml" }

post_upgrade() { # Hint user about ov config file echo ">> ov provides two example config files (ov.yaml, ov-less.yaml) but none of them are echo ">> You can find them here '/usr/share/ov' and here is an example of how to use the de echo ">> $ cp /usr/share/ov/ov.yaml ~/.ov.yaml" }


Thank you . Very nice to have these messages in the PKGBUILD.

But you dont need to copy them to the $HOME folder.

Ov supports the (XDG spec) folder ~/.config/ov/.

It is  better to recommend or suggest that.


From the ov README,

ov will look for a configuration file in the following paths in descending order:

$XDG_CONFIG_HOME/ov/config.yaml
$HOME/.config/ov/config.yaml
$HOME/.ov.yaml

m040601 commented on 2024-02-26 17:48 (UTC) (edited on 2024-02-26 17:55 (UTC) by m040601)

@Julian, thanks !

To everyone,

Don't forget to cast a vote for this tool, With enough votes this might become an official Arch package.

There are currently 3 PKGBUILD's, "ov", "ov-bin" and "ov-git".

YHNdnzj,  https://aur.archlinux.org/pkgbase/ov
kseistrup, https://aur.archlinux.org/pkgbase/ov-bin
Julian, https://aur.archlinux.org/pkgbase/ov-bin

Please collaborate to avoid unnecessary reduplicate work.

Also the author, a japanese guy, has a lot more very interesting related tools, https://noborus.github.io/index.html

There is even an interesting "ovcs",

A client/server version of Terminal Pager ov.

  • By combining terminal pager with client/server and tmux, it became the strongest SQL client

JulianXhokaxhiu commented on 2024-02-26 17:32 (UTC)

Done :)

1 2 Next › Last »