Package Details: grep-git 3.10.r2.gc63a095-1

Git Clone URL: https://aur.archlinux.org/grep-git.git (read-only, click to copy)
Package Base: grep-git
Description: A string search utility
Upstream URL: https://www.gnu.org/software/grep/
Licenses: GPL3
Conflicts: grep
Provides: grep
Submitter: Chocobo1
Maintainer: Chocobo1
Last Packager: Chocobo1
Votes: 0
Popularity: 0.000000
First Submitted: 2017-08-13 15:09 (UTC)
Last Updated: 2023-04-03 06:29 (UTC)

Dependencies (10)

Required by (295)

Sources (1)

Pinned Comments

Chocobo1 commented on 2023-03-20 05:25 (UTC)

@bittin

This message is directed to you: https://aur.archlinux.org/packages/grep-git#comment-903904

Chocobo1 commented on 2023-02-27 10:13 (UTC)

Before you flag this package outdated, read this: **An VCS package is never outdated!!** (unless it won't build or have other issues)

From https://wiki.archlinux.org/title/PKGBUILD#pkgver:
> makepkg can automatically update this variable by defining a pkgver() function in the PKGBUILD.

It means that this package will try to automatically update itself to the latest version every time you build it.

Also see: https://wiki.archlinux.org/title/Arch_User_Repository#What_is_the_difference_between_foo_and_foo-git_packages?

Latest Comments

Chocobo1 commented on 2023-04-03 06:29 (UTC)

Looks like dependency pcre is now pcre2, namcap confirms this after build. Looks like configure option --without-included-regex was removed in 3.7 per note in referenced PKGBUILD on upstream release package.

Thanks, fixed.

noabody commented on 2023-04-02 22:08 (UTC)

See 3.10 arch package

Looks like dependency pcre is now pcre2, namcap confirms this after build. Looks like configure option --without-included-regex was removed in 3.7 per note in referenced PKGBUILD on upstream release package.

Chocobo1 commented on 2023-03-20 05:25 (UTC)

@bittin

This message is directed to you: https://aur.archlinux.org/packages/grep-git#comment-903904

Chocobo1 commented on 2023-02-27 10:13 (UTC)

Before you flag this package outdated, read this: **An VCS package is never outdated!!** (unless it won't build or have other issues)

From https://wiki.archlinux.org/title/PKGBUILD#pkgver:
> makepkg can automatically update this variable by defining a pkgver() function in the PKGBUILD.

It means that this package will try to automatically update itself to the latest version every time you build it.

Also see: https://wiki.archlinux.org/title/Arch_User_Repository#What_is_the_difference_between_foo_and_foo-git_packages?