Arch Linux

orelien

Forum Fellow

From: France

Registered: 2002-12-05

Posts: 220

Website

Rule for package naming

Is there such a rule?

In fact, I'm currently making a package for the clanlib SDK library.
I've got the following problem:
the name of the src file is: ClanLib-0.6.5-1.tar.gz
And it uncompress in a folder "ClanLib-0.6.5"

What will be the name of the package to fit with Arch naming policy?

What value does I should set to $pkgname and $pkgver?
I guess it should be:
$pkgname="<B>clanlib</B>"
$pkgver="<B>0.6.5</B>"

But that makes a dirty PKGBUILD file...
source="URL/.../<B>ClanLib-$pkgver-1</B>.tar.gz"
build()
{
  cd $startdir/src/<B>ClanLib-$pkgver</B>

I would prefer to have something with no name or version hardcoded.
That way, when there is a new release, there is only the $pkgver value to change...

What would do an Arch packager?

I've got the same problem for lots of other "potential" packages I would like to release.
That's a pity that so much archive source files have got a name different from the directory where they uncompress...

Any hints to make a PKGBUILD file as clean as possible would be appreciate.
Thanks

apeiro

Daddy

From: Victoria, BC, Canada

Registered: 2002-08-12

Posts: 771

Website

Re: Rule for package naming

You're correct, the pkgname should be "clanlib".  Don't worry about hardcoding "ClanLib" in a couple spots to make it work.  I've had to do that before too.

orelien

Forum Fellow

From: France

Registered: 2002-12-05

Posts: 220

Website

Re: Rule for package naming

Ok
Thanx for the answer