You are not logged in.
I've read alot that the devs advise against defining your own custom variables in a PKGBUILD file incase the devs add a new variable to the internals of makepkg. But, what if there was an arch dev community supported convention about custom variable definition that was documentated? For example, the docs could say "All custom variables defined in a PKGBUILD should be prefixed with two underscores, e.g. __mycustomvar. This way, there could be custom vars and arch devs wouldn't use any __vars for new features of makepkg.
Just an idea,
-wd
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?
Offline
$origver or $__origver ?
i dont think, it is needed to use non-human_readable__ for PKGBUILD, as it is really elementar (it's not OO for building a whole architecture on it)
my suggestion would be to reserve some variables for some cases
e.g. if pkgver is different than the original version of the tarball, then let's use origver to refer to the original version (the case, when tarball version is 1.0-beta3 and pkgver should be 1.0beta3)
one other is origname where the original name of the pkg is meant (the one the tarball is called after it)
The impossible missions are the only ones which succeed.
Offline
$origver or $__origver ?
i dont think, it is needed to use non-human_readable__ for PKGBUILD, as it is really elementar (it's not OO for building a whole architecture on it)
my suggestion would be to reserve some variables for some cases
e.g. if pkgver is different than the original version of the tarball, then let's use origver to refer to the original version (the case, when tarball version is 1.0-beta3 and pkgver should be 1.0beta3)
one other is origname where the original name of the pkg is meant (the one the tarball is called after it)
I think that is a great idea, since those are the exact instances I run into regularly when creating my own packages, and spawned me to post.
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?
Offline
If you prefix an underscore, you can use any variable you want. I won't introduce any _* variables into makepkg.
Offline
If you prefix an underscore, you can use any variable you want. I won't introduce any _* variables into makepkg.
very cool, thanks apeiro. Is it worth noting this in the official documentation?
-wd
Hobbes : Shouldn't we read the instructions?
Calvin : Do I look like a sissy?
Offline