You are not logged in.

#1 2009-03-02 23:13:08

Ranguvar
Member
Registered: 2008-08-12
Posts: 2,549

Confused about 'provides'

Check this PKGBUILD: http://aur.archlinux.org/packages.php?ID=21002
I've seen this style in a few PKGBUILDs now. Is it really necessary to use =$pkgver in the provides array?

Also, http://www.archlinux.org/packages/extra/x86_64/mpg123/
This package provides, conflicts, and replaces itself. Is that really necessary? Especially the last is a little worrisome.

I'm _not_ criticizing! I don't know enough about PKGBUILDs, and I'd like to learn big_smile

Offline

#2 2009-03-02 23:40:01

Allan
Pacman
From: Brisbane, AU
Registered: 2007-06-09
Posts: 11,400
Website

Re: Confused about 'provides'

Ranguvar wrote:

Check this PKGBUILD: http://aur.archlinux.org/packages.php?ID=21002
I've seen this style in a few PKGBUILDs now. Is it really necessary to use =$pkgver in the provides array?

You do not need to use "foo=$pkgver" with provides but if a package has "depends=("foo>$ver"), the provide will not work without it

Also, http://www.archlinux.org/packages/extra/x86_64/mpg123/
This package provides, conflicts, and replaces itself. Is that really necessary? Especially the last is a little worrisome.

Check it again...  big_smile

Offline

#3 2009-03-03 04:03:21

Ranguvar
Member
Registered: 2008-08-12
Posts: 2,549

Re: Confused about 'provides'

Allan wrote:
Ranguvar wrote:

Check this PKGBUILD: http://aur.archlinux.org/packages.php?ID=21002
I've seen this style in a few PKGBUILDs now. Is it really necessary to use =$pkgver in the provides array?

You do not need to use "foo=$pkgver" with provides but if a package has "depends=("foo>$ver"), the provide will not work without it

So if another package wants to depend on a specific or >/< version of me (me being the main package), I need to 'provide' myself (or whatever other name I'm using in provides) with a specific version? So would it just be good practice to always use =$pkgver in case of someone else's package later needing a specific version of me? Actually, in which case perhaps that should be the default for pacman/makepkg, as I don't think there's a reason _not_ to do =$pkgver? smile

Allan wrote:
Ranguvar wrote:

Also, http://www.archlinux.org/packages/extra/x86_64/mpg123/
This package provides, conflicts, and replaces itself. Is that really necessary? Especially the last is a little worrisome.

Check it again...  big_smile

Ah, durr tongue I had just read up on the history of the two as well. Makes sense now. Damn 123/321.

Offline

Board footer

Powered by FluxBB