Comments (8)
FreeBSD is getting annoying with these fake versions. These are actually caused by the ease of pointing a FreeBSD port to a commit past the tag:
There's no way to detect this pattern through the INDEX file we're using. As Repology maintainer I'd probably mark whole FreeBSD as untrusted after a few more cases, but as FreeBSD port maintainer myself I plan to set up an alternative port metadata dump. FreeBSD portstree contain a lot of useful data not available through INDEX which will be useful for Repology.
@yurivict you may have some comments, as you happen to use this pattern (airspy, flann, amass, swh-lv2 ports).
from repology-rules.
you may have some comments, as you happen to use this pattern (airspy, flann, amass, swh-lv2 ports).
This pattern is used for 2 reasons:
- Projects gave up making regular releases, but are still actively developed in the style of a rolling release
- When the last release doesn't build on FreeBSD, but some later revision does.
Personally, it makes sense to me because this pattern kind-of splits versions and reflects the version as accurately aspossible. It is also partly based on the git's describe
function, and is also consistent with semantic versioning
, see https://semver.org/.
With this pattern being implemented in the ports framework, it is hard to do anything about it. It was suggested to me by [email protected]
and used in a lot of ports.
If the latest released version has some problems, like described above, abandoning this scheme leaved no choice but to not port the project, which is a greater evil than having this type of version, IMHO.
Please note how others do similar things: ntk
project has a particular version , but one distro uses date as a version: http://repology.org/metapackage/ntk/versions
Also libfilteraudio
has the version 0.0.1, but Slack uses 20161122_ada2f4f
: https://repology.org/metapackage/libfilteraudio/versions.
I suggest that you should create a bug report for FreeBSD ports framework here https://bugs.freebsd.org/bugzilla/ , and let them deal with this.
from repology-rules.
FreeBSD should create an additional suffix instead of extending (faking) the version. For example, we use <version>_p<date>
or <version>-r<revision>
in Gentoo.
from repology-rules.
FreeBSD should create an additional suffix instead of extending (faking) the version. For example, we use _p or -r in Gentoo.
Ok, tell this to portmgr.
from repology-rules.
@yurivict I have looked at the freebsd Makefile and didn't get it:
DISTVERSION= 2.6.0-11
DISTVERSIONSUFFIX= -g1ef5a43
What was the reason of faking -11
in that particular case?
I can't find the upstream commit g1ef5a43
and the current release compiles just fine.
from repology-rules.
This isn't faking, this is the way recommended by portmgr. Without -11
it won't get into the version at all.
I agree with you, this isn't an optimal way of dealing with this problem. They should add a tag like DISTVERSIONREV
and put -11
there, and then convert it to _p
or -r
. But I can't do anything about this, this is for portmgr@
.
from repology-rules.
got it, thank you for the explanation
from repology-rules.
- It is faking, because end users see this extra version component
- There is a pretty commonly used schema of
1.2.3git20180915
for which I've suggested a minor extension to make it unambigous (repology/repology-updater#345), and I don't remember portmgr forbidding it. It's explicit in that it's a snapshot, it does not tied to github or git and does not require commits to be on the same branch or exist at all.
from repology-rules.
Related Issues (20)
- Latest CPAN versions not recognized
- 2 "astrodendro" packages should be one
- Codelite versions
- There are 2 different projects called "agenda"
- What's the best way to deal with R-Forge? HOT 5
- Merge tuxtype2
- fs-repo-migrations has an incorrect version in Void Linux HOT 1
- split xivlauncher
- How to xyz-gtk and xyz-gtk3 HOT 1
- Swiften has nothing to do with the Swift language
- KDE's 6th Megarelease - Alpha HOT 2
- tor-browser versions
- Remove warning for Npackd repositories HOT 15
- Better handling of ncurses versioning? HOT 1
- fix some missing quotes HOT 2
- Suricata has 2 active branches: 6.0.x and 7.0.x HOT 5
- Merge yt-dlp-nightly from Terra into yt-dlp
- Remove warning for Npackd repositories 2 HOT 1
- Add warning to the Chocolatey repositories.
- Incorrect/Different project versions causes other repositories to be marked outdated HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from repology-rules.