-
Notifications
You must be signed in to change notification settings - Fork 251
Commit
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -23,7 +23,7 @@ | |
|
||
void dexed_trace(const char *source, const char *fmt, ...); | ||
|
||
#define DEXED_ID "0.9.4" | ||
#define DEXED_ID "0.9.4hf1" | ||
This comment has been minimized.
Sorry, something went wrong.
This comment has been minimized.
Sorry, something went wrong.
asb2m10
Author
Owner
|
||
|
||
#ifdef DEBUG | ||
#define DEXED_VERSION DEXED_ID " DEBUG" | ||
|
1 comment
on commit 73a266d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the Arch Linux User Repository (AUR) there are VCS packages, which are always compiled from the latest state of the source code repository of the project. I maintain a VCS package for dexed here: https://aur.archlinux.org/packages/dexed-git/ For the purpose of these packages it does not matter whether a version number designates an official release or not. But if the project's version is reflected in the AUR package's version, as I like to do it, it should conform to the versioning scheme of Arch packages, so that the system's package manager knows, which version is older or newer. Others just use a revision number and/or the hash of the latest commit as the package version, but I like to include the project's real version number, so it's easier to compare a VCS package to the stable package for a project (e.g. https://aur.archlinux.org/packages/dexed/).
This will be considered as a lower version than the previous one by most versioning schemes, which can lead to problems with distribution packages, since they will consider this version a downgrade.